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

Improve monitoring errors #2785

Open
3 of 7 tasks
lambdanis opened this issue Aug 9, 2024 · 0 comments
Open
3 of 7 tasks

Improve monitoring errors #2785

lambdanis opened this issue Aug 9, 2024 · 0 comments
Labels
area/metrics Related to prometheus metrics

Comments

@lambdanis
Copy link
Contributor

lambdanis commented Aug 9, 2024

  • Review tetragon_errors_total and other "errors" metrics
  • Stop reporting non-errors (as in: no action needed) as errors. Define separate metrics for "casual fails" if needed.
  • Refactor errors metrics to make them more useful (all of these are subject to review)
    • Delete tetragon_errors_total{type="handler_error"} - it duplicates handler_errors_total
    • Consider further splitting tetragon_errors_total
    • Consider merging event cache errors metrics into one with event_type and entry_type labels
    • Consider merging kprobe ok and errors metrics into one with status label
  • Standardize on error label (rather than error_type, type, etc)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/metrics Related to prometheus metrics
Projects
Development

No branches or pull requests

1 participant