From b054e394d15d9bf50b05f89695320bcfa8b19c2f Mon Sep 17 00:00:00 2001 From: Tony Murray Date: Tue, 31 Oct 2023 17:01:36 -0500 Subject: [PATCH] Update Rules.md --- doc/Alerting/Rules.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/Alerting/Rules.md b/doc/Alerting/Rules.md index 8806963aa2..d9f95575ec 100644 --- a/doc/Alerting/Rules.md +++ b/doc/Alerting/Rules.md @@ -72,9 +72,10 @@ On the Advanced tab, you can specify some additional options for the alert rule: - An example of this would be an average rule for all CPUs over 10% ```sql -SELECT devices.*, (SELECT AVG(processors.processor_usage) as sub_avg FROM processors WHERE processors.device_id = devices.device_id - HAVING AVG(processors.processor_usage) >= 10) as cpu_avg -FROM devices WHERE devices.device_id = ? AND (devices.status = 1 && (devices.disabled = 0 && devices.ignore = 0)) = 1; +SELECT devices.*, (SELECT AVG(processors.processor_usage) as sub_avg FROM processors +WHERE processors.device_id = devices.device_id HAVING AVG(processors.processor_usage) >= 10) as cpu_avg +FROM devices WHERE devices.device_id = ? AND +(devices.status = 1 && (devices.disabled = 0 && devices.ignore = 0)) = 1; ``` > The 10 would then contain the average CPU usage value, you can