New option clear_alarm_always (#5050)
##### Summary Netdata after restart might clear the status of previous alarm to UNINITIALIZED. In that case in Alerta we can have a status not cleared correctly. It is not a problem to send it once again because Alerta does deduplication of alerts by itself. ##### Component Name health/notifications ##### Additional Information It is just additional variable in health_alarm_notify.conf
Piotr Roszatycki committed
Dec 20, 2018 at 15:05 UTC
7bf4c597765af12618d24b9ede67190547c3e18f
2 files changed
+9
-1
health/notifications/alarm-notify.sh.in
+1
-1
@@ -243,7 +243,7 @@ then
243
fi
244
245
# don't do anything if this is CLEAR, but it was not WARNING or CRITICAL
246
-if [ "${old_status}" != "WARNING" -a "${old_status}" != "CRITICAL" -a "${status}" = "CLEAR" ]
246
+if [ "${clear_alarm_always}" != "YES" -a "${old_status}" != "WARNING" -a "${old_status}" != "CRITICAL" -a "${status}" = "CLEAR" ]
247
then
248
info "not sending notification for ${status} of '${host}.${chart}.${name}' (last status was ${old_status})"
249
exit 1
health/notifications/health_alarm_notify.conf
+8
@@ -126,6 +126,14 @@ aws=""
126
# here in most cases.
127
#logger_options=""
128
129
+#------------------------------------------------------------------------------
130
+# extra options
131
+
132
+# By default don't do anything if this is CLEAR, but it was not WARNING or CRITICAL.
133
+# You can send it always if your system makes deduplication for alarms.
134
+#clear_alarm_always='YES'
135
+
136
+#
137
#------------------------------------------------------------------------------
138
# NOTE ABOUT RECIPIENTS
139
#