Ad Widget

Collapse

After upgrade to 2.0 triggers are not reflecting the real state

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • orkaa
    Junior Member
    • Jul 2012
    • 3

    #1

    After upgrade to 2.0 triggers are not reflecting the real state

    Before the upgrade I was running 1.8.5 with a bunch of offline hosts. The overview page was all gray, only the 'unreachable' triggers were red. That was the behavior I expected.

    Then I upgraded to 2.0 and the 'unreachable' (agent.ping) triggers were all red as before but all the other triggers that should have been grey were now green!

    The image displayed on the overview page wasn't really consistent with the real state. Yeah sure, the last time triggers were checked, they were ok but the last check is now long gone so they shouldn't be green if that's not the actual state.

    I've figured that I can solve this by depending all triggers on the unreachable one but this makes the overview page kind of messy with all the extra 'arrow' icons on triggers.

    Why did this work before the upgrade? And what are the correct steps for solving it?
    Last edited by orkaa; 17-07-2012, 16:59.
  • orkaa
    Junior Member
    • Jul 2012
    • 3

    #2
    some more tests

    I've done some more tests now.

    I installed a fresh zabbix 2.0 just for testing and created a few hosts that don't actually exist - hostname is set to some random word. They appeared blinking green on the overview page but after 1800 seconds they weren't blinking anymore. They were just green. This is just... WRONG?!

    I mean, there's a host that doesn't even exist and zabbix is showing that everything is perfectly fine with it. The only indication that something is wrong is on the Triggers page (info says: zabbix agent unavailable) but that also went away after 1800 seconds!

    I like zabbix very much and have been using it for a few years now but this really scares me! If I'm monitoring hundreds of hosts I certainly don't want a false feeling that everything is OK when in reality there's a disaster waiting to happen.

    Please tell me that I'm doing something awfully wrong.

    Comment

    • Alex_G
      Junior Member
      • Sep 2010
      • 8

      #3
      Any news on this?

      This makes me want to roll back to 1.83. Is there a fix coming for this or whats going on?

      Comment

      • orkaa
        Junior Member
        • Jul 2012
        • 3

        #4
        bump

        Zabbix, please tell us if this will be fixed in the near future or should we just implement something similar with trigger dependencies (which unfortunately makes the overview page really ugly)

        Comment

        • ploochan
          Member
          • Oct 2009
          • 42

          #5
          were you able to figure this out? I have upgraded from 1.8.3 to 2.0.3 and I can see that I can add a new host but when I test the triggers it doesn't work. I see that the host is still green when the unable to ping should be red. But in the latest data shows the right information

          Comment

          Working...