Graylog2 / Graylog2/graylog2-server
ISW: Routing to streams via pipeline rules leads to pipelines connected to Default Stream being executed
- Dominant language
- Java
- Stars
- 8.1k
- Forks
- 1.1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 217
Description
## Expected Behavior
When I create an input with the new input setup wizard and let it create a stream & enable "Remove matches from ‘Default Stream’" (all nicely separated), no other pipelines besides the one that is created will be run for messages ingested into that input.
## Current Behavior
When pipelines are pre-existing that are connected to the "Default Stream", those will be executed for all messages coming in to another input which has its own stream & index set, has "Remove matches from ‘Default Stream’" configured, but is routed through pipelines.
## Possible Solution
Set up stream routing through ISW with generic stream rules instead of pipelines?
## Steps to Reproduce (for bugs)
1.
2.
3.
4.
## Context
## Your Environment
* Graylog Version:
* Java Version:
* OpenSearch Version:
* MongoDB Version:
* Operating System:
* Browser version:
## Checklist
[] This issue fix need to be backported.
[] Does this issue have **security** implications?
Contributor guide
Assessment
This issue has not been assessed yet.