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

Probe status not checked if device is not responding to ping or snmp

Details

    Description

      After a device became offline (ping or snmp), the attached probe isn't checked (because it's a polling module) and remains in "OK" status until the device became online again. Than probe's status and graphs misleads users about the checked services availability.

      Suggesting to check probes before ping or snmp check in poller.

      Attachments

        Activity

          [OBS-3896] Probe status not checked if device is not responding to ping or snmp

          Hi Fabian Koszta, we have not received the additional information requested earlier from you in this issue 'After a device became offline (ping or snmp), the attached probe isn't checked (because it's a polling module) and remains in "OK" status until the device became online again. Than probe's status and graphs misleads users about the checked services availability.

          Suggesting to check probes before ping or snmp check in poller.'!

          Issues without your response will be closed within 2 weeks.

          landy Mike Stupalov added a comment - Hi Fabian Koszta, we have not received the additional information requested earlier from you in this issue 'After a device became offline (ping or snmp), the attached probe isn't checked (because it's a polling module) and remains in "OK" status until the device became online again. Than probe's status and graphs misleads users about the checked services availability. Suggesting to check probes before ping or snmp check in poller.'! Issues without your response will be closed within 2 weeks.

          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

          Note, this comment is added automatically.

          bot Observium Bot added a comment - 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 Note, this comment is added automatically.

          People

            landy Mike Stupalov
            fabian.koszta Fabian Koszta
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: