I'm fairly new to zabbix, we've previously used Solarwinds Server & Application Monitor and I'm trying to do some of the same things we used to do there.
Here's an example.
We have a item that monitors a remote .crl file to make sure that it's not expiring with x days.
I want to have a trigger action that sends a message between say Monday - Friday 9am-5pm so I'm not waking someone up in the middle of the night. I thought that I would be able to create a trigger action that has the conditions of
Event name contains "CRL Expiration"
AND
Time period in 1-5,09:00-17:00
So if my CRL Expiration item becomes a problem at say 3am, I was expecting the zabbix problem page to show it right away, but that the action would happen at 9am.
is that the way it's supposed to work? I've done some testing and it doesn't seem that way. I see the item show up on the problem page right away, however when the time period becomes current, It doesn't do my actions I'd expect. (a slack message in this case)
Here's an example.
We have a item that monitors a remote .crl file to make sure that it's not expiring with x days.
I want to have a trigger action that sends a message between say Monday - Friday 9am-5pm so I'm not waking someone up in the middle of the night. I thought that I would be able to create a trigger action that has the conditions of
Event name contains "CRL Expiration"
AND
Time period in 1-5,09:00-17:00
So if my CRL Expiration item becomes a problem at say 3am, I was expecting the zabbix problem page to show it right away, but that the action would happen at 9am.
is that the way it's supposed to work? I've done some testing and it doesn't seem that way. I see the item show up on the problem page right away, however when the time period becomes current, It doesn't do my actions I'd expect. (a slack message in this case)
Comment