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

[Meta] Alerting-Infra requirements #76914

Open
gmmorris opened this issue Sep 8, 2020 · 1 comment
Open

[Meta] Alerting-Infra requirements #76914

gmmorris opened this issue Sep 8, 2020 · 1 comment
Labels
apm:alerting Feature:Alerting Meta Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability

Comments

@gmmorris
Copy link
Contributor

gmmorris commented Sep 8, 2020

This is a meta issue for the Alerting team to keep track of the different requirements raised by Infra.

Below is a table of requirements identified in @Crazybus 's POC into using Alerting for Infra's needs:

Status Requirement Owning Team Relevant Issue(s) Notes Infra Priority
Open Alerting is not separated out per monitor in Uptime Monitor Alert Type @elastic/uptime #74659 Might have been addressed by #74659 🎉 Medium
Closed. Should be delivered in 7.11 Close a PagerDuty incident when a monitor's Alert resolves @elastic/kibana-alerting-services #49405 #76908 #77772 We will first have to add Open Blocker
Open Separate criteria for "down" and "recovery" in Uptime Monitor Alert Type (error rate is over 75% for an event window, recovery requires 0% for the same event window.) @elastic/uptime ?   High
Open There is no Certificate expiry Alert Type (@elastic/uptime ? )   Someone will have to develop this custom Alert Type, it might be APM, but I don't want to speak for them. 🤷‍♂️ low
Open Programmatic creation of Alerts @elastic/kibana-alerting-services   We do provide a full HTTP API and we have the CLI tool @pmuellr created, which isn't officially supported by the team. We will discuss this in the Alerting team. Blocker
Open Adjust the sensitivity/severity and action configuration of alerting per monitor @elastic/uptime & @elastic/kibana-alerting-services   This might require some investigation and clearer requirements, but this should be possible as far as the framework is concerned, but would require work on the APM side. I suspect it the implementation might be blocked on #64077, but that totally depends on how APM choose to implement this. Medium
Open Alerting logic that will handle flappy alerting with different collection durations @elastic/uptime ?   High
Open Ability to include extra information links to documentation for troubleshooting the down service or links to other places like our Inventory in Pager Duty Action @elastic/kibana-alerting-services #76910   High
Open Creating alerts per multiple columns in Metric Threshold Alert Type @elastic/uptime ?   medium
Open Preview in Metric Threshold Alert Type @elastic/uptime ?   low
Open Index Threshold doesn't support filtering @elastic/kibana-alerting-services #66046 This is hasn't been prioritised for 7.x, as we're hoping APM's AlertTypes can cover your needs, but I'll raise that this has come up again and we might reprioritise medium
Open There is no alert type which supports Elasticsearch Query DSL combined with Painless scripting @elastic/kibana-alerting-services #61313 high
@gmmorris gmmorris added Feature:Alerting apm:alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability labels Sep 8, 2020
@mikecote mikecote added the Meta label Sep 8, 2020
@mikecote
Copy link
Contributor

mikecote commented Sep 8, 2020

@gmmorris this is great! Can we also update the team dependencies on alerting meta issue as well and add a section there? We're be using that issue as the source of truth but it can reference this issue for further details (similar to SIEM).

@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apm:alerting Feature:Alerting Meta Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability
Projects
None yet
Development

No branches or pull requests

3 participants