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

Add alert checking for Disk I/O or Disk status

Details

    • Improvement
    • Resolution: Incomplete
    • Major
    • None
    • Professional Edition
    • Alerting
    • net-snmp / debian

    Description

      This week, we had a issue where, in one of our ceph nodes, a disk went offline and we only noticed way to late. Looking at our monitoring/Observium, we realized that the disk going offline wasn't really being registered anywhere. The quick fix we want to try is to create a alert for zero disk I/O, which should not occur on a online disk.

      However, It seems that there is no way to create an alert for Disk I/O?

      Any better alternative to catch such an event (/dev/sda going offline) would be appreciated as well.

      Attachments

        Activity

          [OBS-4679] Add alert checking for Disk I/O or Disk status

          Ok, I guess this issue can be closed, then.

          simon.giotta@ruag.ch Simon Giotta added a comment - Ok, I guess this issue can be closed, then.

          The best way to handle this sort of thing is via syslog alerts.

          Disk I/O isn't an "entity" in Observium at present, so it's not exposed to the alerting system.

          adama Adam Armstrong added a comment - The best way to handle this sort of thing is via syslog alerts. Disk I/O isn't an "entity" in Observium at present, so it's not exposed to the alerting system.

          no snmpdump is required.

          simon.giotta@ruag.ch Simon Giotta added a comment - no snmpdump is required.

          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
            simon.giotta@ruag.ch Simon Giotta
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: