Ad Widget

Collapse

Problem don't switch automatically to "Resolved"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • starterks
    Junior Member
    • Apr 2024
    • 1

    #1

    Problem don't switch automatically to "Resolved"

    I have the problem that the nodata function in Zabbix does not work, I use an external script which reads data from an API.
    There I get alertname, severity and status, but I have created triggers for each severity I get from there, so 4 trigger prototypes in total,
    and now I have set it up as an expression like this: last(/Template Name/alert.severity[{#STATUS}_{#SEVERITY}_{#ALERTNAME}])="critical"
    For each severity 1 prototype with this expression depending on the severity.
    And as soon as the problem no longer exists, nothing more is read from the API, i.e. the problem should switch to "Resolved" in Zabbix,
    but this does not happen, it simply disappears in Zabbix and that is not the goal,
    I tried it this way with the recovery expression: nodata(/Template Name/alert.severity[{#STATUS}_{#SEVERITY}_{#ALERTNAME}],1m)=1
    Unfortunately it didn't work, does anyone know more?
Working...