Ad Widget

Collapse

trigger name not consistantly displayed correctly

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • drp
    Junior Member
    • Oct 2011
    • 4

    #1

    trigger name not consistantly displayed correctly

    I have a trigger with an expression looking at 5 different item values, and the trigger name includes the values of those items. I know the trigger expression and name are valid and work. The problem is they don't display correctly in some places...

    in the default zabbix dashboard, there are two sections that display the trigger: 'system status' and 'last 20 issues'. you can see from the attached image that when I hover over the 'system status' section the trigger name includes the values of the item. However, the 'last 20 issues' section does not show up correctly. More importantly, when alerts get sent out to users about the problem, the trigger info that is included in the email doesn't show up correctly.

    All of this had been working fine recently. in the specific case shown in the image, the host named 'tiki' was changed to use template_b instead of template_a, where template_b was created as a copy of template_a. Very little was changed between the two templates, mostly just the name and some of the time intervals.

    Any ideas as to what could be causing this? I can't imagine it is a problem with the items or triggers, since they do display correctly in some locations.

    zabbix version is 1.8.4
    Attached Files
  • drp
    Junior Member
    • Oct 2011
    • 4

    #2
    trigger info

    trigger expression:
    Code:
    (({Template_Core_Servers:hrStorageRemaining13.last(0)}<{Template_Core_Servers:space_threshold.last(0)})&({Template_Core_Servers:hrStorageUsedPercent13.last(0)}>{Template_Core_Servers:percent_threshold.last(0)}))|({Template_Core_Servers:hrStorageDescr13.str('#@!')}=1)
    trigger name:
    Code:
    {HOSTNAME} - Storage '{ITEM.VALUE5}' has used {ITEM.VALUE3} percent of available space ({ITEM.VALUE1} MB remaining)
    this had all worked fine until I switched it to use a different template...

    Comment

    • drp
      Junior Member
      • Oct 2011
      • 4

      #3
      solved

      the problem seemed to be because the history was set to 0 for the items involved in the trigger. I seem to recall that they were set to 0 in the original template before this problem occurred, and if they hadn't already been set to 0, I know for sure that I didn't recently make that change.

      So not sure exactly what changed between the old and new templates, but I've set the history to a minimum of 1 day for those items, and now it is working.

      Comment

      Working...