graylog-plugin-pipeline-processor
graylog-plugin-pipeline-processor copied to clipboard
plugins/org.graylog.plugins.pipelineprocessor/system/pipelines/connections includes stream IDs for which no stream exists
trafficstars
Problem description
Output of GET plugins/org.graylog.plugins.pipelineprocessor/system/pipelines/connections lists streams as connected to pipelines for the stream IDs of which no stream exists (anymore, perhaps due to deletion).
Steps to reproduce the problem
- GET the output of plugins/org.graylog.plugins.pipelineprocessor/system/pipelines/connections in a Graylog setup with pipeline-stream connections
- Cross-reference the stream_id values in the returned array against the /streams endpoint, e.g. GET /stream/$streamid to check if it exists or not.
- Result: Some streams in the output do not exist!
Environment
- Graylog Version: 2.2.3 (Upgraded from 2.2.2 in a much-used setup)
- Pipeline Processor plugin version: 2.2.3
- Elasticsearch Version: 2.4.4
- MongoDB Version: 3.4.3
- Operating System: Debian Jessie 8.7
- Browser version: Firefox 52.0.2