Ad Widget

Collapse

Zabbix 4.0: suppress problems during maintenance period

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • s0r1n
    Junior Member
    • Feb 2013
    • 23

    #1

    Zabbix 4.0: suppress problems during maintenance period

    After an upgrade from 3.0.24 to 4.0.3 the problem notifications are received after the maintenance period (with delay).
    Before the upgrade it worked as expected.

    Here the current setup:
    * Maintenance type: "No data collection"
    * "Problem is not suppressed" in action configuration
    * "Pause operations for suppressed problems" option in action configuration is checked (new in 4.0)
    Resulted behaviour: the problem notifications are not suppressed, they were received after the maintenance period.

    If the following option from setup is changed (the other options remain unchanged):
    * "Problem is suppressed" in action configuration
    Then suddently no emails from Zabbix are received at all!!! (The problems are shown in Dashboard only)

    How to suppress (and not to delay) the problems during the maintenance period?
  • s0r1n
    Junior Member
    • Feb 2013
    • 23

    #2
    Actually after the maintenance period notifications with 'Zabbix agent is unreachable' occur. It seems the agent is not reachable during maintenance.
    How to avoid these notifications? There didn't occur in version 3.0...

    Comment

    • troffasky
      Senior Member
      • Jul 2008
      • 567

      #3
      Is your maintenance period "With data collection" or not? Perhaps that might be it, although if a no-data-collection maintenance period causes an alarm about lack of data then that's just silly!

      Comment

      • s0r1n
        Junior Member
        • Feb 2013
        • 23

        #4
        Indeed, "With data collection" set up no alarms will raise after the maintenance period.

        Comment

        • taken
          Junior Member
          • May 2015
          • 15

          #5
          heya guys,
          Exacly same problem here with Zabbix 4.0.5.
          I create Maintenance with no data collection, because we upgrade servers and after the maintenance period i get XX e-mails with:

          Problem started at 03:25:20 on 2019.03.13
          Problem name: Zabbix agent on haproxy1 is unreachable for 5 minutes
          Host: haproxy1
          Severity: Average
          Original problem ID: 1392

          After less than 1 minute i get:
          Problem has been resolved at 03:25:55 on 2019.03.13
          Problem name: Zabbix agent on haproxy1 is unreachable for 5 minutes
          Host: haproxy1
          Severity: Average
          Original problem ID: 1391

          This is amazing bad - i use this function in 3.X and never get any so much spam on e-mail looks like BUG in 4.X ?

          Best Regards
          TaKeN
          Last edited by taken; 13-03-2019, 05:34.

          Comment

          • Vorbiks
            Junior Member
            • Mar 2019
            • 1

            #6
            Hi guys!
            I have this problem with Maintenance period like Taken.
            Is there any solution?
            Version: Zabbix 4.0.5
            Works through zabbix proxy

            Comment

            • christian.g
              Junior Member
              • Jun 2019
              • 1

              #7
              Same problem here.

              Due the update from 3x version to 4x version the option "Maintenance mode - no data collection" are generating some issues.

              Even activating the Maintenance option "without data collection" are generating the "SLA accounting" problem.

              Any soluction?

              Comment


              • christian.g
                christian.g commented
                Editing a comment
                I found the situation, and the error was mine.

                Normally i create a "Maintenance period" - without data collection, and at the same moment start the service/server maintenance, don't waiting the service enter in maintenance.

                i've observed, that the service or server enter in maintenance mode 1 minute later than the "start period", and only later this 1 minute i can start my tasks. So, i can start the maitenance, and don't take impact about the "SLA TIME"

                Thank you about the experience.
            Working...