Module: check_mk
Branch: master
Commit: d63c167af1d2fb9561ce34c1a9fa246a6d037962
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=d63c167af1d2fb…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Wed Jan 15 09:44:27 2014 +0100
Draft for rule based notifications updated
---
doc/drafts/README.rule_based_notifications | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/drafts/README.rule_based_notifications
b/doc/drafts/README.rule_based_notifications
index 1c16b99..dbbcc57 100644
--- a/doc/drafts/README.rule_based_notifications
+++ b/doc/drafts/README.rule_based_notifications
@@ -43,9 +43,9 @@ The condition can be formed of:
* the event type (up, down, ok, crit, etc.)
* a host specification like in WATO rules (using host tags, etc.)
* a service specification using regular expressions (like in WATO rules)
+* The original state or the complete state transition (e.g. CRIT -> WARN vs. OK ->
WARN)
Further conditions that we can think of are:
-* The original state or the complete state transition (e.g. CRIT -> WARN vs. OK ->
WARN)
* the type of the check plugin, e.g. only checks of type "if" or
"if64"
* whether the host or service is contained in a certain host/service group
* whether it's contained in a certain contact group