Availability and Trigger period condition
Hello,
we need a workaround (or a solution, better) to resolve an issue we have.
We use zabbix to check PCs availability (if they're reachable on network or switched on). We also need not to receive any message if this condition doesn't happen in a certain time period.
We don't use period restriction in actions because it could give us wrong informations. I.e.:
Action is configured to suspend messages between 22.00 and 6.00.
if a PC switched off at 22.15 a trigger is generated but no message is sent (and it is ok for us). BUT: if the same PC doesn't switch on any longer we don't receive any message, because no trigger is raised again after 6.00 o' clock.
So we thought to use period condition in the trigger itself:
BUT! agent.ping.time(0) works only if agent is reachable.
Is there a way to build up such a condition, taking the time period from another item always available? (server itself, or some trick)
Thanks
we need a workaround (or a solution, better) to resolve an issue we have.
We use zabbix to check PCs availability (if they're reachable on network or switched on). We also need not to receive any message if this condition doesn't happen in a certain time period.
We don't use period restriction in actions because it could give us wrong informations. I.e.:
Action is configured to suspend messages between 22.00 and 6.00.
if a PC switched off at 22.15 a trigger is generated but no message is sent (and it is ok for us). BUT: if the same PC doesn't switch on any longer we don't receive any message, because no trigger is raised again after 6.00 o' clock.
So we thought to use period condition in the trigger itself:
Code:
({Template X:agent.ping.nodata(300)}=1) & ({Template X:agent.ping.time(0)}>123000) & ({Template X:agent.ping.time(0)}<220000)
Is there a way to build up such a condition, taking the time period from another item always available? (server itself, or some trick)
Thanks