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

Recover alerts not being resolved at Pagerduty

Details

    • Help
    • Resolution: Fixed
    • Major
    • None
    • None
    • Default
    • None

    Description

      Hi

      After upgrading to version 24.3.13376 from version 24.2.13341, i noticed that recover notifications are not resolving alerts at Pagerduty.

      Once i reverted to version 24.2.13341 it started working again

      Are you aware of any changes that can affect this?

      For example Slack notifications kept working fine, i got the alert and the recover alerts.

       

       

       

      Attachments

        Activity

          [OBS-4782] Recover alerts not being resolved at Pagerduty
          Shama Tarek added a comment -

          Thanks !!

          Shama Tarek added a comment - Thanks !!
          landy Mike Stupalov added a comment -

          Should be fixed in r13377.

          landy Mike Stupalov added a comment - Should be fixed in r13377.
          Shama Tarek added a comment -

          You can see below in the screenshot tests that i did and you can notice that the last alert was successfully resolved by integration API while the previous one i had to manually resolve

           

          Shama Tarek added a comment - You can see below in the screenshot tests that i did and you can notice that the last alert was successfully resolved by integration API while the previous one i had to manually resolve  
          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.

          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: