Windows Service Monitoring: Unterschied zwischen den Versionen
Aus Wiki-WebPerfect
Admin (Diskussion | Beiträge) |
Admin (Diskussion | Beiträge) |
||
| Zeile 1: | Zeile 1: | ||
== Trigger if the service has 3 times a "wrong" status == | == Trigger if the service has 3 times a "wrong" status == | ||
'''Exmaple:''' You monitor a Zabbix Item, in this examaple the FailoverCluster-Service (service.info[ClusSvc]) with an interval of 30secs.<br> | '''Exmaple:''' You monitor a Zabbix Item, in this examaple the FailoverCluster-Service (service.info[ClusSvc]) with an interval of 30secs.<br> | ||
| − | You want to trigger if the last 3 values are not "0" but if the service does not exists then trigger should not alert ( | + | You want to trigger if the last 3 values are not "0" but if the service does not exists then trigger should not start/alert (because of Nodes that are not in a cluster).<br> |
''The Zabbix Template "Compute_Hyper-V" are linked to the Hyper-V Nodes.'' | ''The Zabbix Template "Compute_Hyper-V" are linked to the Hyper-V Nodes.'' | ||
Aktuelle Version vom 24. März 2020, 10:56 Uhr
Trigger if the service has 3 times a "wrong" status
Exmaple: You monitor a Zabbix Item, in this examaple the FailoverCluster-Service (service.info[ClusSvc]) with an interval of 30secs.
You want to trigger if the last 3 values are not "0" but if the service does not exists then trigger should not start/alert (because of Nodes that are not in a cluster).
The Zabbix Template "Compute_Hyper-V" are linked to the Hyper-V Nodes.
Value 0 means the Windows Service is running.
Value 255 means Zabbix find no Windows Service with this name (No such service).
Mostly incorrectly configured (misconceived)
Zabbix Trigger expression:
({Compute_Hyper-V:service.info[ClusSvc].last(3)}<>0) and ({Compute_Hyper-V:service.info[ClusSvc].last(3)}<>255)
-> This is not working correctly.
Correct configuration would be
({Compute_Hyper-V:service.info[ClusSvc].count(#3,0)}=0) and ({Compute_Hyper-V:service.info[ClusSvc].count(#3,255)}=0)
