This repository was archived by the owner on Mar 21, 2023. It is now read-only.

Description
Problem description

While the Graylog web interface provides some information about the error rate an individual rule produces, there's no way to find out what kind of errors these are.
Neither the web interface nor the logs of Graylog provide any hints about the details of these errors nor which messages have been affected.
Steps to reproduce the problem
- Write a rule which produces some kind of runtime error
- Attach the rule to a pipeline which is attached to a stream
- Send messages into that stream
- Watch error counter for rule increase
- ❓
- PROFIT!
Environment
- Graylog Version: 2.4.1
- Pipeline Processor plugin version: 2.4.1
- Elasticsearch Version: 5.6.5
- MongoDB Version: 3.x
- Operating System: Ubuntu Linux (in Docker)