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

Printer Supply Alert Checkers Recovery Alert Behavior

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Alerting
    • Observium Professional 23.2.12527

    Description

      We trigger a warning when a toner supply is "le 20%", and have the "send recovery notification" toggled to true.  Receiving subsequent "null" check result (i.e. timeout) triggers the recovery notification.  There is no option to delay the recovery notification, like there is for the initial alert (or the recovery notification appears to be ignoring it).

      Then, the next time the checker runs it re-triggers the original printer supply warning.

      Attachments

        Activity

          [OBS-4425] Printer Supply Alert Checkers Recovery Alert Behavior
          landy Mike Stupalov added a comment -

          Should be fixed in r12551.

          landy Mike Stupalov added a comment - Should be fixed in r12551.
          landy Mike Stupalov added a comment -

          Ok I see which trouble, recover send when no data received from printer..

          landy Mike Stupalov added a comment - Ok I see which trouble, recover send when no data received from printer..
          NegwerIT Scott Driemeier-Showers added a comment -

          [^myagent.snmpwalk]

          NegwerIT Scott Driemeier-Showers added a comment - [^myagent.snmpwalk]
          NegwerIT Scott Driemeier-Showers added a comment -

          And the alert E-mails.  First the "recovery" at 15:11pm, then the re-"Alert" at 15:56 (following the delay rule).

          NegwerIT Scott Driemeier-Showers added a comment - And the alert E-mails.  First the "recovery" at 15:11pm, then the re-"Alert" at 15:56 (following the delay rule).
          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 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -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 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -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
            NegwerIT Scott Driemeier-Showers
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: