Maybe I just understood something wrong.
I have some services, which go critical/warn and back to OK within minutes (which is more or less insignificant, e.g. a high memory usage on a build server for a compiler run)
I set for the services in question a notification delay via wato:
Wato – host& service configuration – Monitor configuration – notification – delay service notification
Delay: 3
Conditions: hostage is ping only
Explicit host: some hosts
Specify explicit service: “PING”
Nevertheless I get “ok -> warn” mail and “war -> OK” for that hosts with a 1 min gap. So where is my mistake here?
Frank Lienhard
Neos**IT GmbH
Schachtweg 1
38440 Wolfsburg
Tel. +49 5361 83494-32
Fax +49 5361 83494-94
mailto:frank.lienhard@neos-it.de
http://www.neos-it.de/
Handelsregister: Amtsgericht Braunschweig, HRB 203557
Geschäftsführer: Sven Wosny
Hi Frank,
the delay is never active for changes -> OK. This is by design. Of Nagios.
Mathias
···
Am 21.02.2013 15:30, schrieb Lienhard, Frank:
Maybe I just understood something wrong.
I have some services, which go critical/warn and back to OK within
minutes (which is more or less insignificant, e.g. a high memory usage
on a build server for a compiler run)
I set for the services in question a notification delay via wato:
Wato � host& service configuration � Monitor configuration �
notification � delay service notification
Delay: 3
Conditions: hostage is ping only
Explicit host: some hosts
Specify explicit service: �PING�
Nevertheless I get �ok -> warn� mail and �war -> OK� for that hosts with
a 1 min gap. So where is my mistake here?
Frank Lienhard
/N�eos//IT/**GmbH**
Schachtweg 1
38440 Wolfsburg
Tel. +49 5361 83494-32
Fax +49 5361 83494-94
mailto:frank.lienhard@neos-it.de
http://www.neos-it.de/
Handelsregister: Amtsgericht Braunschweig, HRB 203557
Gesch�ftsf�hrer: Sven Wosny
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en