Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  2. ZBXNEXT-721

ability to silence a single trigger for a defined timeperiod (maintenance for a single trigger, or non-permanent acknowledgement)


    • Icon: New Feature Request New Feature Request
    • Resolution: Fixed
    • Icon: Major Major
    • 6.2.0rc1, 6.2 (plan)
    • 1.8.4
    • None
    • Sprint 89 (Jun 2022), Sprint 90 (Jul 2022)
    • 10

      We need a way to support the following workflow:

      • Something breaks on Saturday at 5pm. Zabbix sends an alert. (This exists already.)
      • Staff receives the alert, triages it, decides it's not truly urgent, and silences that alert until Monday at 9am.
      • Sunday at 9am another trigger for the same host generates an alert, which is received and resolved by staff.
      • Monday at 9am alerts for the Saturday 5pm event start being sent again.

      As I understand it the two possibilities today are:

      ACKNOWLEDGE the alert and configure the Action to ignore events which have been acknowledged. But there's no time limit – once acknowledged, an Action is silent forever. If alerts could have a time limit ("ACKNOWLEDGE for 24 hours") that would solve this use case.

      Schedule the entire host for maintenance. But then if the problem gets worse or another trigger fires, we won't find out. So if we could schedule a trigger on an individual host for maintenance, this would solve the use case.

        1. blinking_icon.gif
          626 kB
          Sergejs Maklakovs
        2. far_problem_suppression_validation_issue.gif
          990 kB
          Sergejs Olonkins
        3. image-2022-06-02-11-21-55-123.png
          12 kB
          Elina Pulke
        4. image-2022-06-02-11-23-07-793.png
          12 kB
          Elina Pulke
        5. image-2022-06-07-15-31-01-159.png
          49 kB
          Andrejs Zazuks
        6. implementation_example1.jpg
          373 kB
          Vadim Ipatov
        7. implementation_example2.jpg
          318 kB
          Vadim Ipatov
        8. incorrect_prefilled_date_and_time.gif
          808 kB
          Sergejs Olonkins
        9. issues_with_problem_in_maintenance_suppression.gif
          2.59 MB
          Sergejs Olonkins
        10. Screenshot from 2022-05-30 13-20-19.png
          27 kB
          Sergejs Olonkins
        11. Screenshot from 2022-05-30 16-07-32.png
          45 kB
          Sergejs Olonkins
        12. Screenshot from 2022-05-30 17-45-52.png
          16 kB
          Sergejs Olonkins
        13. Screenshot from 2022-05-30 17-46-25.png
          16 kB
          Sergejs Olonkins
        14. Selection_999(1639).png
          28 kB
          Sergejs Maklakovs
        15. Selection_999(1642).png
          67 kB
          Sergejs Maklakovs
        16. Selection_999(1644).png
          28 kB
          Sergejs Maklakovs
        17. Selection_999(1647).png
          238 kB
          Sergejs Maklakovs
        18. Selection_999(1648).png
          168 kB
          Sergejs Maklakovs
        19. Selection_999(1649).png
          34 kB
          Sergejs Maklakovs
        20. Selection_999(1654).png
          132 kB
          Sergejs Maklakovs
        21. Selection_999(1655).png
          100 kB
          Sergejs Maklakovs
        22. Selection_999(1656).png
          26 kB
          Sergejs Maklakovs
        23. suppress-and-unsuppress-icons.png
          20 kB
          Miks Kronkalns
        24. wrong_icon_in_actions_column.gif
          912 kB
          Sergejs Olonkins

            Miks.Kronkalns Miks Kronkalns
            harpo Will Lowe
            Team B
            42 Vote for this issue
            49 Start watching this issue