Pipeline to stream

[igoriceg (Igor)]

Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question.
Don’t forget to select tags to help index your topic!

1. Describe your incident:
Don’t work pipeline rules

2. Describe your environment:

• OS Information:

• Package Version: graylog-server 7.1.3, graylog-datanode 7.1.3

• Service logs, configurations, and environment variables:

  Message processor

  #	Processor	Status
  1	AWS Instance Name Lookup	active
  2	Pipeline Processor	active
  3	Stream Rule Processor	active
  4	Message Filter Chain	active
  5	GeoIP Resolver	active

=========================================

Hi community, i already have been installed greylog 5 + opensearch, and there was a worked chain - pipeline rules+pipelines and also was worked chain of processor message

thats ok

and about a week ago i make decision an upgrade this by deleting opensearch and graylog and install graylog-server + graylog-datanode 7.1.3 instead olders version.

I restored all my configs (from screenshots thats i made before deleting old ones) - and all works fine unlike pipeline rules

[igoriceg (Igor)]

if i trying simulate working pipelines via Simulator - i see a new fields, but in production - nothing happened

[Wine_Merchant]

Hello @icsj2007,

Good to see you update to the newest release.

Below is the default process order, I would recommend that you use this unless there is some specific reason it was altered. In the current order, pipelines play out before routing to streams.

[igoriceg (Igor)]

big thx, ill try it today

but also i want to know - is there any possible way to log message processor ?

[igoriceg (Igor)]

big thx to @Wine_Merchant

its really help) even if it was by default)