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

[Alerting] Add telemetry to count number of failed or unrecognized rule tasks #122985

Closed
ymao1 opened this issue Jan 13, 2022 · 1 comment · Fixed by #123856
Closed

[Alerting] Add telemetry to count number of failed or unrecognized rule tasks #122985

ymao1 opened this issue Jan 13, 2022 · 1 comment · Fixed by #123856
Assignees
Labels
Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@ymao1
Copy link
Contributor

ymao1 commented Jan 13, 2022

As part of #119650 we've identified the current scenarios where a rule task might become failed or unrecognized (causing the rule to silently stop being claimed) and determined that these cases are very limited. However, we should add telemetry to track the counts of rule tasks in these states to try to pro-actively identify when we've introduced a bug or regression that causes this state to start occurring more frequently.

@ymao1 ymao1 added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework labels Jan 13, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants