-
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
[Alerting] Phase 4 of AoA: Visualize and alert on available data #122367
Labels
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
chrisronline
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Jan 5, 2022
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
kobelb
removed
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Jan 31, 2022
kobelb
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Jan 31, 2022
Pinging @elastic/response-ops (Team:ResponseOps) |
kobelb
changed the title
[Alerting] Phase 4 of AoA: Visualize and alert on available data
[Alerting] Phase 4 of AoA: Visualize and alert on available data
Jan 31, 2022
chrisronline
moved this to In Progress
in AppEx: ResponseOps - Rules & Alerts Management
May 20, 2022
Repository owner
moved this from In Progress
to Done
in AppEx: ResponseOps - Rules & Alerts Management
Jun 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Meta: #120542
Once the data is available in Stack Monitoring indices, we need to decide how we want to use that data - what charts/UIs we want to build as well as deciding what out-of-the-box rules should exist to let users know when performance problems arise. We also need to figure out where this data can live - we need to be concerned with how Stack Monitoring data is stored and how it currently doesn’t leverage Kibana security and privileges. The best place is going to be the Stack Monitoring UI itself but other options are something we should consider.
Here is some sample screenshots from a PoC PR:
We should also add out of the box alerts within the Stack Monitoring system to automatically notify users when various thresholds are reached.
The text was updated successfully, but these errors were encountered: