Ad Widget

Collapse

Unexpected notification behaviour after Maintenance

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • arli
    Member
    • Jan 2008
    • 71

    #1

    Unexpected notification behaviour after Maintenance

    After upgrading from 1.8.3 to 1.8.4 I started to get recovery notifications at the end of the maintenance window about hosts that went through maintenance and recovered inside that window.

    I reviewed the release notes and found this:
    [DEV-433] added generation events after maintenance period if trigger status changed during this period
    I don't know where to find more information about that... since I can't access DEV tasks in Jira.
    My question is, what should I do to not get those kind of notifications? Because in my perspective, there isn't nothing wrong with those triggers.

    I'm using Normal event generation .
    Attached Files
    Last edited by arli; 25-01-2011, 20:01.
  • arli
    Member
    • Jan 2008
    • 71

    #2
    I downgraded zabbix to 1.8.3 at the moment, to avoid unnessesary notifications.
    But now... all of you out the, who are also taking advantage of maintenance periods and are upgraded to latest version. Don't you have such problem?

    Comment

    • mjsr
      Junior Member
      • Feb 2011
      • 15

      #3
      Late (ok, really late) answer but, on 1.8.4, still suffering the same "issue".

      The changelog on 1.8.5 doesn't seem to handle that.

      Commented that on another thread: http://www.zabbix.com/forum/showthre...4385#post84385

      Cheers,

      Comment

      • igor
        ZABBIX Support Specialist
        • Mar 2009
        • 40

        #4
        You can get rid of these notifications if you will perform the following changes:

        1. In the configuration of your action from "Action conditions" you should remove option "trigger value = "OK"" and leave option "Trigger value = "PROBLEM"" and also leave option "Maintenance status not in "maintenance"";

        2. Turn on (enable) recovery messages in this action;

        Comment

        • mjsr
          Junior Member
          • Feb 2011
          • 15

          #5
          Hello,

          Some coworkers detected the issue in the source code of timer.c (or time.c).

          That should be integrated in Zabbix 1.8.6.

          Comment

          • Andreas Bollhalder
            Senior Member
            Zabbix Certified Specialist
            • Apr 2007
            • 144

            #6
            Is this problem fixed ?

            I have upgraded Zabbix from 1.8.2 to 1.8.6 and got this problem too. So it seems that it isn't fixed in 1.8.6.

            In the release notes of 1.8.7, I read that the default conditions of the actions are "Trigger value = Problem" and "Not in maintenance" . Does it work if I add "Trigger value = Problem" (which I currently don't use) or must I downgrade to 1.8.3, which seems the last version without the problem ?

            Edit: I don't like to configure the "Recovery Message", because I worked fine before. But if there is no other way ...

            Thanks in advance.

            Andreas
            Last edited by Andreas Bollhalder; 19-09-2011, 08:41.
            Zabbix statistics
            Total hosts: 380 - Total items: 12190 - Total triggers: 4530 - Required server performance: 224.2

            Comment

            Working...