Ad Widget

Collapse

Paging, but only during work hours.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • JeremiahMN
    Junior Member
    • May 2016
    • 2

    #1

    Paging, but only during work hours.

    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)
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    Originally posted by JeremiahMN
    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
    Unfortunately, that's not what "Time period in" means. What it actually means is "Problem Event was created during ...".

    See my old post where my site tried to do something similar: https://www.zabbix.com/forum/zabbix-...erting-periods

    Zabbix would really benefit from a "Current Time in" option in the action setup.
    Last edited by tim.mooney; 11-10-2024, 10:01.

    Comment

    Working...