Ad Widget

Collapse

nodata() doesn't seem to work for deleted oid's

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • WouterPeeters
    Junior Member
    • Jun 2024
    • 6

    #1

    nodata() doesn't seem to work for deleted oid's

    I have a discovery rule that discovers an oid of alarms on a chassis.
    This gives me an {#SNMPINDEX} where I create item for severity, status, ...
    When the alarm clears on the chassis the chassis deletes the {#SNMPINDEX}.
    For when the alarm gets cleared on the chassis, I created a nodata()=1 trigger.
    This trigger never go's of. However I can create a nodata()=0 trigger and this will show me all the {#SNMPINDEX} that have data.
    (I did create the nodata trigger after the oid got deleted)

    It seems the nodata checks what gets returned on the last check, but no more checks occur because the oid no longer exists.

    How do i solve this? Can I create a trigger on the age of the last result?
  • Markku
    Senior Member
    Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
    • Sep 2018
    • 1782

    #2


    sec parameter can be used to check if there is no data during last X time.

    Markku

    Comment

    • WouterPeeters
      Junior Member
      • Jun 2024
      • 6

      #3
      For some reason that doesn't work. I used:
      Code:
      changecount(/host/key, 10m)=0
      To check if there where 0 new values in the last 10 minutes.
      A trigger with this code gives the opposite result and shows all the items with data in the last 10 minutes.

      Is there a way to test the result of changecount(/host/key, 10m)?

      Comment

      Working...