# Another pipleline question

**URL:** <https://community.graylog.org/t/another-pipleline-question/22629>\
**Category:** Graylog Central (peer support)\
**Tags:** pipeline-rules\
**Created:** [February 14, 2022, 3:51am UTC](https://community.graylog.org/t/another-pipleline-question/22629 "2022-02-14T03:51:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mosman](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@mosman](https://community.graylog.org/u/mosman)\
**Post date:** [February 14, 2022, 3:51am UTC](https://community.graylog.org/t/another-pipleline-question/22629/1 "2022-02-14T03:51:24Z")

</div>

Hello dear community,  
after now four hours of scratching my head I thought it’s time to ask…

I am fairly new to Graylog so perhaps I just misunderstood things.  
I have a Syslog Input which is filled by various linux servers. All messages do appear in “All messages” stream. OI now created another stream “All Syslog” where I put messages in that belong to a specific computer (do not look at the names, it’s just a test). This works too. Whenever I click on the specific stream in the Streams-Page the messages just for that server are shown.  
I now create a pipeline with a simple rule as stage 0:rule “create\_syslog\_fields”  
when  
has\_field(“message”)  
then  
debug(“Pipeline Create Syslog-Test1”);  
end

I connect the created pipeline with the Stream “All Syslog” and nothing happens (no Debug message in the log), If I connect the pipeline to the stream “All messages” it works as expected.  
What am I doing wrong?

**2. Describe your environment:**

- OS Information:  
OpenSuse 15.3

- Package Version:  
Graylog 4.2  
Elasticsearch 7.10.2

- Service logs, configurations, and environment variables:

**3. What steps have you already taken to try and solve the problem?**  
see text above

**4. How can the community help?**  
I need help understanding why the messages from the stream “All SYSLOG” are not parsed in the pipeline

---

<div class="post-metadata">

**Author:** ![mosman](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@mosman](https://community.graylog.org/u/mosman)\
**Post date:** [February 14, 2022, 4:07am UTC](https://community.graylog.org/t/another-pipleline-question/22629/2 "2022-02-14T04:07:29Z")

</div>

I forgot: The streams configuration has a rule:  
_gl\_source\_input_ **must** match input _Linux-Server Input (Syslog UDP: 6205f301d3dde703302d8f7a)_

---

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [February 14, 2022, 6:50pm UTC](https://community.graylog.org/t/another-pipleline-question/22629/3 "2022-02-14T18:50:05Z")

</div>

> [@mosman](#):
>
> created another stream “All Syslog” where I put messages in that belong to a specific computer

How are you routing the specific server messages into the All Syslog stream?

Also, what is your message Processor Configuration set up - look for it under System-\> configurations. People are often caught with having the “pipeline Processor” on the wrong side of the “Message Filter Chain”. You likely want hte “Message Filter Chain” to run before (have a lower number) the 'Pipeline Processor"

---

<div class="post-metadata">

**Author:** ![mosman](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@mosman](https://community.graylog.org/u/mosman)\
**Post date:** [February 14, 2022, 11:14pm UTC](https://community.graylog.org/t/another-pipleline-question/22629/4 "2022-02-14T23:14:41Z")

</div>

**Hello and thank you for the reply.**  
**I created a stream with the stream rule of "must match input of “Linux-Server input”, as mentioned above.**  
**As I said, the messages do appear in the stream (when using search).**  
**As for the chain of processing, it is AWS Instance Name lookup (unused by me), followed by GeoIP Resolver, followed by Pipeline Processor, followed by Message Filter chain.**  
**-----**  
**And that did the trick.Changing the order so that Message filter chain is before Pipeline processing does now invoke the pipeline just as I want it.**  
**Thank you for that pointer**  
**Cheers**

---

<div class="post-metadata">

**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\
**Post date:** [February 15, 2022, 4:56pm UTC](https://community.graylog.org/t/another-pipleline-question/22629/5 "2022-02-15T16:56:41Z")

</div>

Great! Mark it as the answer for future searchers please! 😃

---

<div class="post-metadata">

**Author:** ![mosman](https://avatars.discourse-cdn.com/v4/letter/m/c6cbf5/32.png) [@mosman](https://community.graylog.org/u/mosman)\
**Post date:** [February 15, 2022, 10:55pm UTC](https://community.graylog.org/t/another-pipleline-question/22629/6 "2022-02-15T22:55:27Z")

</div>

Done that just now 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [March 1, 2022, 10:55pm UTC](https://community.graylog.org/t/another-pipleline-question/22629/7 "2022-03-01T22:55:38Z")

</div>

Closed on March 1, 2022, 10:55pm UTC

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
