-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Add reason handler to the alerting framework #95908
Labels
Comments
sorenlouv
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Mar 31, 2021
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
sorenlouv
removed
Feature:Alerting
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
labels
Mar 31, 2021
I removed the alerting team since they are no longer a dependency for this. Instead the reason handler will be part of the rule registry that @dgieselaar is working on. |
mikecote
added
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Team:APM
All issues that need APM UI Team support
and removed
needs-team
Issues missing a team label
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
labels
Apr 8, 2021
Pinging @elastic/apm-ui (Team:apm) |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Generic mechanism to generate "human readable reason" on alerts.
Similar capability to the security raw renderer.
First version will be an "hardcoded" reason defined in the product, users cannot customize it.
The text was updated successfully, but these errors were encountered: