Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4855

recovery notification not being triggered for some alerts

Details

    • Help
    • Resolution: Not A Bug
    • Major
    • None
    • None
    • Default
    • None

    Description

      Hi
      I am using version 24.6.13594 (25th June 2024) and i noticed that i dont get recovery notification for some alerts

      Attachments

        Activity

          [OBS-4855] recovery notification not being triggered for some alerts

          Furthermore, the status that was alerted has been deleted, so it will obviously never generate a recovery:

          Presumably the fan sensor which was also alerted was deleted at the same time.

          Make sure you're looking at the correct things. You're confusing a fan sensor and a fan status indicator for the Power supply status.

          adama Adam Armstrong added a comment - Furthermore, the status that was alerted has been deleted, so it will obviously never generate a recovery: Presumably the fan sensor which was also alerted was deleted at the same time. Make sure you're looking at the correct things. You're confusing a fan sensor and a fan status indicator for the Power supply status.

          The alerts and recoveries in the screenshot are not for the same things.

          adama Adam Armstrong added a comment - The alerts and recoveries in the screenshot are not for the same things.
          Shama Tarek added a comment -

          At the device i am also able to see that everything is back to normal

           

          Shama Tarek added a comment - At the device i am also able to see that everything is back to normal  
          Shama Tarek added a comment -

          You can see in the screenshot that there were recovery in the eventlog, but i dont see it at the alert log and i didnt get a slack recover message too.

          Shama Tarek added a comment - You can see in the screenshot that there were recovery in the eventlog, but i dont see it at the alert log and i didnt get a slack recover message too.

          General questions and device support can be discussed in our Discord channel, click here to join.


          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            Shama Tarek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: