Ad Widget

Collapse

Why did triggered Problem Change to Resolve on it's own

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ggearon
    Junior Member
    • Jun 2024
    • 4

    #1

    Why did triggered Problem Change to Resolve on it's own

    Hello, I recently setup an alert to email when an interface status triggers the "interface down" trigger. I'm using the built in template Cisco Nexus. Basically we set some interfaces to administratively down. We received alerts that the interfaces went down. Great, expected that. Then 6 hours later, we receive alerts that the problem, is resolved. On all the ports we set to down. Why did Zabbix do this? Is it just because of the trigger expression? Here is the expression, right from the template trigger.

    Expression: {$IFCONTROL:"Ethernet1/45"}=1
    and last(/SwitchName/net.if.status[436230144])=2
    and change(/SwitchName/net.if.status[436230144])
Working...