Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • Professional Edition
    • Alerting
    • None

    Description

      We have an Alert Checker sending an email alert when a device is down/unreachable using the following test condition:

      device_status notequals 1

      The email alert generated contains a graph of "device_ping" referencing ping.rrd. This test condition has worked well for many years.

      However, if the device SNMP setting are set to "Skip ICMP echo checks, only SNMP availability.", no ping.rrd exists and the graph in the email alerts shows pink with "Error Drawing Graph". Clicking the broken graph reveals a message noting the missing ping.rrd file.

      Unfortunately ICMP is not available or relevant for all the devices we monitor due to NAT and port redirects required at some locations.

      Might be better to reference ping_snmp.rrd in cases where Ignore Ping is enabled?

      Attachments

        1. email_alert.png
          email_alert.png
          36 kB
        2. RRD_error.png
          RRD_error.png
          3 kB

        Activity

          [OBS-4864] Broken Graph in Email Alerts

          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

            adama Adam Armstrong
            rhebert Ryan Hébert
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: