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

Schedule-based muting of alerts #66055

Closed
arisonl opened this issue May 11, 2020 · 5 comments
Closed

Schedule-based muting of alerts #66055

arisonl opened this issue May 11, 2020 · 5 comments
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@arisonl
Copy link
Contributor

arisonl commented May 11, 2020

As a user I want to be able define a schedule based on which selected alerts can be muted. As an example in the case of known downtimes, to account for known seasonality etc.

@arisonl arisonl added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels May 11, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@pmuellr
Copy link
Member

pmuellr commented May 14, 2020

Is there another solution that's doing anything calendar-related like this? I'm thinking there is, but not sure which one.

I wonder if this will be simpler with cron support? Can these schedules be specified easily as cron expressions (guessing not, but worth poking at a bit more?)

I think there's an implication that you'd be setting a schedule on multiple alerts, and perhaps these scheduled mutes should be searchable/sortable for UI purposes.

Could there be multiple mute schedules for an alert? Can a single mute schedule include multiple date ranges?

Do we need support at the instance level, or is at the alert level good enough?

I wonder if we can fit this into the current schedule property? Eg, as a peer of interval, named muted?

"schedule": {
"properties": {
"interval": {
"type": "keyword"
}
}
},

@mikecote
Copy link
Contributor

mikecote commented Jun 3, 2020

Similar to #65706?

@mikecote
Copy link
Contributor

Closing in favour of #65706.

@bradquarry
Copy link

bradquarry commented Jun 10, 2020

@pmuellr just as a reference our ML UI does this. Turn off modeling during a window.

@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
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

No branches or pull requests

6 participants