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

[Observability Alerting][R&D] Implement/verify cancellation for observability rules #123053

Closed
3 tasks done
jasonrhodes opened this issue Jan 14, 2022 · 2 comments
Closed
3 tasks done
Assignees
Labels
epic Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" v8.4.0

Comments

@jasonrhodes
Copy link
Member

jasonrhodes commented Jan 14, 2022

The alerting team (@elastic/kibana-alerting-services) has recently implemented new tools for auto-canceling/timeouts[1][2] for alerting rules. We should (a) become familiar with these new APIs, and (b) determine if we should be adjusting our rule configs or executor logic to take advantage of these new APIs.

Acceptance Criteria

  • Implementation tickets are created, if needed, to address cancellation/timeout for existing observability rule types
  • In particular, we should look at the Metrics Threshold, Metrics Inventory, and Log Threshold rule types
@jasonrhodes jasonrhodes added R&D Research and development ticket (not meant to produce code, but to make a decision) Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" labels Jan 14, 2022
@mikecote
Copy link
Contributor

cc @elastic/response-ops

@simianhacker
Copy link
Member

This has been implemented globally by the Response Ops team 💃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" v8.4.0
Projects
None yet
Development

No branches or pull requests

4 participants