From 60dfd89a6ce4ef897cfedf695bbb340577c89d69 Mon Sep 17 00:00:00 2001 From: Kim Pohas Date: Wed, 11 Dec 2024 11:12:42 -0800 Subject: [PATCH 1/3] Update static monitor eval frequency --- docs/alerts/monitors/create-monitor.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/alerts/monitors/create-monitor.md b/docs/alerts/monitors/create-monitor.md index 178e348689..21f879bb71 100644 --- a/docs/alerts/monitors/create-monitor.md +++ b/docs/alerts/monitors/create-monitor.md @@ -139,10 +139,10 @@ Triggers are evaluated by balancing the requirement of timely alert notification * For [static logs monitors](#static-detection-method), triggers are similar to "Alert when the result is greater than _ within Y Minutes". The triggers are evaluated periodically as below. | When detection window (Y) is | Evaluate trigger every | |:-----------------------------|:-----------------------| - | 30m or less | 1m | - | 30m to 3h | 2m | - | 3hr to 12h | 10m | - | Greater than 12h | 20m | + | Less than 15m | 1m | + | 15m to 1h | 2m | + | 1h to 6h | 10m | + | 6h to 1d | 20m | * For [anomaly logs monitors](#anomaly-detection-method), triggers are evaluated every `timeslice` as specified in the monitor query. For example, the below query is evaluated every 2 minutes. ``` _sourceCategory=Labs/Apache/Access From 305eb22c59702ff354f7fcb0f6d6d64e3d3630f8 Mon Sep 17 00:00:00 2001 From: "Kim (Sumo Logic)" <56411016+kimsauce@users.noreply.github.com> Date: Wed, 11 Dec 2024 19:10:40 -0800 Subject: [PATCH 2/3] Update docs/alerts/monitors/create-monitor.md --- docs/alerts/monitors/create-monitor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/alerts/monitors/create-monitor.md b/docs/alerts/monitors/create-monitor.md index 21f879bb71..1d55e83117 100644 --- a/docs/alerts/monitors/create-monitor.md +++ b/docs/alerts/monitors/create-monitor.md @@ -142,7 +142,7 @@ Triggers are evaluated by balancing the requirement of timely alert notification | Less than 15m | 1m | | 15m to 1h | 2m | | 1h to 6h | 10m | - | 6h to 1d | 20m | + | Greater than 6h | 20m | * For [anomaly logs monitors](#anomaly-detection-method), triggers are evaluated every `timeslice` as specified in the monitor query. For example, the below query is evaluated every 2 minutes. ``` _sourceCategory=Labs/Apache/Access From 94482bfc5aa2c2c1a9b862e891f6c7cd5614a0ef Mon Sep 17 00:00:00 2001 From: "Kim (Sumo Logic)" <56411016+kimsauce@users.noreply.github.com> Date: Wed, 11 Dec 2024 19:11:57 -0800 Subject: [PATCH 3/3] Update docs/alerts/monitors/create-monitor.md --- docs/alerts/monitors/create-monitor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/alerts/monitors/create-monitor.md b/docs/alerts/monitors/create-monitor.md index 1d55e83117..8d2061dc99 100644 --- a/docs/alerts/monitors/create-monitor.md +++ b/docs/alerts/monitors/create-monitor.md @@ -139,7 +139,7 @@ Triggers are evaluated by balancing the requirement of timely alert notification * For [static logs monitors](#static-detection-method), triggers are similar to "Alert when the result is greater than _ within Y Minutes". The triggers are evaluated periodically as below. | When detection window (Y) is | Evaluate trigger every | |:-----------------------------|:-----------------------| - | Less than 15m | 1m | + | 15m or less | 1m | | 15m to 1h | 2m | | 1h to 6h | 10m | | Greater than 6h | 20m |