add node level AR based example (#13684)
add node level anomaly rate based example
Andrew Maguire committed
Oct 3, 2022 at 16:47 UTC
31a46c5412df7d093267364fdf32cef368b1b939
1 file changed
+19
-2
health/health.d/ml.conf
+19
-2
@@ -1,10 +1,26 @@
1
# below are some examples of using the `anomaly-bit` option to define alerts based on anomaly
2
# rates as opposed to raw metric values. You can read more about the anomaly-bit and Netdata's
3
# native anomaly detection here:
4
-# https://learn.netdata.cloud/docs/configure/machine-learning#anomaly-bit---100--anomalous-0--normal
4
+# https://learn.netdata.cloud/docs/agent/ml#anomaly-bit---100--anomalous-0--normal
5
6
# examples below are commented, you would need to uncomment and adjust as desired to enable them.
7
8
+# node level anomaly rate example
9
+# https://learn.netdata.cloud/docs/agent/ml#node-anomaly-rate
10
+# if node level anomaly rate is between 1-5% then warning (pick your own threshold that works best via tial and error).
11
+# if node level anomaly rate is above 5% then critical (pick your own threshold that works best via tial and error).
12
+# template: ml_1min_node_ar
13
+# on: anomaly_detection.anomaly_rate
14
+# os: linux
15
+# hosts: *
16
+# lookup: average -1m foreach anomaly_rate
17
+# calc: $this
18
+# units: %
19
+# every: 30s
20
+# warn: $this > (($status >= $WARNING) ? (1) : (5))
21
+# crit: $this > (($status == $CRITICAL) ? (5) : (100))
22
+# info: rolling 1min node level anomaly rate
23
+
24
# alert per dimension example
25
# if anomaly rate is between 5-20% then warning (pick your own threshold that works best via tial and error).
26
# if anomaly rate is above 20% then critical (pick your own threshold that works best via tial and error).
@@ -33,4 +49,5 @@
49
# every: 30s
50
# warn: $this > (($status >= $WARNING) ? (5) : (20))
51
# crit: $this > (($status == $CRITICAL) ? (20) : (100))
36
-# info: rolling 5min anomaly rate for system.cpu chart
\ No newline at end of file
52
+# info: rolling 5min anomaly rate for system.cpu chart
53
+