Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISW - Input Diagnosis Improvements #21326

Open
1 of 9 tasks
grotlue opened this issue Jan 10, 2025 · 2 comments · May be fixed by #21337
Open
1 of 9 tasks

ISW - Input Diagnosis Improvements #21326

grotlue opened this issue Jan 10, 2025 · 2 comments · May be fixed by #21337
Assignees

Comments

@grotlue
Copy link
Contributor

grotlue commented Jan 10, 2025

  • Received Message count by Stream: clickable link to stream
    • We need to adjust the API system/inputs/diagnostics/${inputId} to include the stream id so we can build a link
  • Message Failed metrics: clickable link to Failures stream (with input and time filter)
  • Content for Input Diagnosis step in input setup wizard (@tellistone, we need copy for that)
  • Use correct metrics
  • Add new metric org.graylog2.inputs.${inputId}.failures.input as the asterix notation in org.graylog2.inputs.codecs.*.${inputId}.failures does not work
  • Add feature tests
  • The current metrics are per second, should we keep them? If yes, should we make it clear to the user? @tellistone
@grotlue
Copy link
Contributor Author

grotlue commented Jan 10, 2025

We cannot build a link for "Message Error at Input" as we don't save them yet
@AntonEbel can you check if and how we can build links to "Message Failed to process" and "Message Failed to index" (using failure_type field?)

@grotlue grotlue linked a pull request Jan 13, 2025 that will close this issue
9 tasks
@grotlue grotlue linked a pull request Jan 13, 2025 that will close this issue
9 tasks
@grotlue
Copy link
Contributor Author

grotlue commented Jan 14, 2025

All three metrics we use are per second metrics. I checked with @tellistone and it is preferred to not use per second metrics but rather a "total in the last 15 min" metric. Can we add new metrics for that @AntonEbel?

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

Successfully merging a pull request may close this issue.

2 participants