Skip to content
This repository has been archived by the owner on Mar 21, 2023. It is now read-only.

No information about rules errors #242

Open
joschi opened this issue Jan 21, 2018 · 3 comments
Open

No information about rules errors #242

joschi opened this issue Jan 21, 2018 · 3 comments

Comments

@joschi
Copy link
Contributor

joschi commented Jan 21, 2018

Problem description

Rules error indicator

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

  1. Write a rule which produces some kind of runtime error
  2. Attach the rule to a pipeline which is attached to a stream
  3. Send messages into that stream
  4. Watch error counter for rule increase
  5. 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)
@inventor96
Copy link

inventor96 commented Oct 26, 2018

Isn't this the purpose of the "gl2_processing_error" field?

I'd be interested in knowing how to reset that error counter...

@joschi
Copy link
Contributor Author

joschi commented Oct 26, 2018

Isn't this the purpose of the "gl2_processing_error" field?

That field only exists if the message was indexed at all.

@inventor96
Copy link

That field only exists if the message was indexed at all.

Ahh, true. I didn't think about that case.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants