Uptime Monitor Alert Maintenance Window

wwalker · August 25, 2023, 3:21pm

I have an uptime monitor configured to look at a website. There is an automated task that restarts SQL for this application, which causes an HTTP 5xx code during restart. This causes the uptime monitor to report the site as down. I'd like to create a window in the monitor to not alert during this timeframe. I've tried the below filters on the monitor config, but it says it's going to match all monitors and not this specific one. How can I create a window for this monitor to not report down between 04:45 - 5:05 UTC?

Reg Ex timestamp
monitor.id : example.contoso.net AND NOT @timestamp >= /\d{4}-\d{2}-\d{2}T04:45.*/ AND NOT @timestamp <= /\d{4}-\d{2}-\d{2}T05:05.*/

KQL Wildcard timestamp
monitor.id : example.contoso.net AND NOT @timestamp >= *T04:45* AND NOT @timestamp <= *T05:05*

jsanz · September 4, 2023, 1:33pm

Unfortunately at this moment maintenance windows affect all rules. There is already a feature request to allow filtering as described here

github.com/elastic/kibana

[Maintenance Windows] Support "filtering" what Rules/Alerts Maintenance Windows affect

opened 01:33AM - 20 Aug 23 UTC

BenB196

Team:ResponseOps

**Describe the feature:** The new maintenance window feature is a great conce…pt, however, it has one serious flaw; it affects all rules in the space during the maintenance window. I'd like to be able to "filter" the Rules/Alerts that the maintenance window will affect. **Describe a specific use case for the feature:** Maintenance windows are great because they allow for suppressing notifications while doing work, however, in their current implementation, they suppress _all_ alerts for _all_ rules in a space. A few reasons why this can be an issue. ## Use Case 1 Suppose I want to work on System A, and not have notifications for this system. If I add a Maintenance window, now I won't get alerts if System B has an issue, even though I really want to get alerts from System B, as I'm not actively working on this system. ## Use Case 2 Similar to Use Case 1, but slightly different, suppose `Operations Team A` and `Operations Team B`, both operate out of a shared space `Observability`. If `Operations Team A` wants to do work on their systems and they add a Maintenance Window, then `Operations Team B` will now not get notified if one of there rules fires. In both of the use cases above, Maintenance Windows now become a "dangerous" feature as they have the real possibility of hiding issues that aren't intended to be hidden. (I think something similar to the recently added Conditional Actions functionality, would be a relatively robust fit for Maintenance Windows to make them more effective)

Feel free to chime in there with more details or feedback as you see fit.

system · October 2, 2023, 1:34pm

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.