Ad Widget

Collapse

Alerts present after changing conditions

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • aseques
    Member
    • May 2019
    • 40

    #1

    Alerts present after changing conditions

    I am using a custom template based on the PDU template by HP to monitor metrics about some power outlets https://github.com/zabbix/community-...du_(traps)/6.0

    With this trigger I was getting alerts for all the PDU outlets that didn't have a temperature probe (they always return 0 as the temperature and triggers an alert)

    Code:
    last(/CPDB-PDU-RACK2/Temperature) > last(/CPDB-PDU-RACK2/TemperatureThUpperCritical)
    I added the condition to check if they have a temperature probe (then TemperatureProbeStatus is > 1) and some that don't (TemperatureProbeStatus is = 1), so now the logic is this:
    Code:
    last(/CPDB-PDU-RACK2/Temperature) > last(/CPDB-PDU-RACK2/TemperatureThUpperCritical) and last(/CPDB-PDU-RACK2/TemperatureProbeStatus)>1

    I can test git the read values and it seems to be fine

    Click image for larger version

Name:	imatge.png
Views:	129
Size:	90.2 KB
ID:	484063

    The issue is that for all the triggers that we already triggered, the alert status doesn't go away, I tried supressing the errors but they reappear afterwards.
    Click image for larger version

Name:	imatge.png
Views:	70
Size:	39.0 KB
ID:	484064
    Any ideas on what might be wrong?
Working...