Ad Widget

Collapse

Trigger status unknown on overview

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bcheese
    Junior Member
    • Jun 2006
    • 26

    #1

    Trigger status unknown on overview

    I have a number of SNMP monitored environmental devices which I have located around one of my data centres. These devices provide me with both the current temperature and the humidity readings of the room. As there are a number of them, I have setup a template for the monitors and created 2 hosts linked to the template.

    Polling for the data is correct. I have the current values and I have a history of values.

    Triggers operate correctly. I have verified this by looking on the Monitoring -> Triggers page.

    Display on the Monitoring -> Overview is incorrect. They alway show that the status as unknown. Whereby they are currently (according to the Triggers page) FALSE.

    I have also tried creating an item and trigger directly on the Host itself, with the same result being visible.

    Any ideas?
  • bcheese
    Junior Member
    • Jun 2006
    • 26

    #2
    I a little curious that I am the only one who has noticed this issue, but hey, thats OK. below is a corrected segment of include/triggers.inc.php file, note that I have line numbers switched on in vim. The line I added was the break which is now line 1139, which was allowing any trigger which was false to fall through and be reclassified (for display purposes) to show as unknown.


    Code:
    1132                     switch($trhosts[$hostname]['value'])
    1133                     {
    1134                         case TRIGGER_VALUE_TRUE:
    1135                             $style = get_severity_style($trhosts[$hostname]['priority']);
    1136                             break;
    1137                         case TRIGGER_VALUE_FALSE:
    1138                             $style = 'normal';
    1139                             break;
    1140                         default:
    1141                             $style = 'unknown_trigger';
    1142                     }

    Comment

    • frankdh
      Junior Member
      • Feb 2007
      • 3

      #3
      Its odd that no one else commented on this, but this is definitely a bug in 1.3.2.

      Thanks bcheese for providing a fix.

      Comment

      Working...