Details

    • New Feature
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery, Ports
    • None

    Description

      This is a feature request for new classes for sensor and for port types.

      New classes:

      sensors class=distance (in meters)

      I think it would be great to have a new class for distance.
      I was faced with the need for a new class when I was preparing a patch for BDCOM in OBS-3648.
      This patch is for EPON OLT that can report the distance to the client device.
      Track is useful for monitoring unauthorized line lengthening or diagnostics of signal strength problems.
      Distance can also be obtained from many switches (on copper ports) that support cable diagnostics.
      For example on snr-switch (DCN like):

      mtivi@tlife-hs:/opt/observium$ snmpbulkwalk -v2c -c *** -Pud -Ih -OQUsb <hostname> SNR-SWITCH-MIB::vctLastStatus.8
      vctLastStatus.8 = "
      Interface Ethernet1/0/8:
      -----------------------------------------------
      Cable pairs     Cable status    Length (meters)
      -----------     ------------    ---------------
      (1, 2)          open            5
      (3, 6)          open            5
      (4, 5)          open            5
      (7, 8)          open            6
      "

      index 8 = ifIndex
      In future we can discover distance for this port. I don't know how to discover that now.

      sensors class=bitrate

      I found digital decoder PBI DCH-4000P, I am working on patch for this device...
      This device is used for decode signal from satellite (DVB-S) to cable (DVB-C) or to multicast for IPTV.
      It have a metric for bitrate of signal , for example (in bps):

      snmpbulkwalk -v2c -c *** <hostname> PBI-4000P-5000P-MIB::tunerValidBitrate
      PBI-4000P-5000P-MIB::tunerValidBitrate.0 = INTEGER: 54602688

      sensors class=frequency

      this class is already exists, but I found a problem for save this metric when I prepare a patch for digital decoder PBI DCH-4000P.

      snmpbulkwalk -v2c -c *** <hostname> PBI-4000P-5000P-MIB::tuner-sInput
      PBI-4000P-5000P-MIB::lnbFrequency.0 = INTEGER: 9750
      PBI-4000P-5000P-MIB::satFrequency.0 = INTEGER: 11880
      ...

      lnbFrequency and satFrequency in MHz.
      When I use

      'scale'               => 1000000,

      I have SQL WARNINGS : Out of range value for column 'sensor_value' at row 1, and Observium shows 1000MHz.
      So we need a new class (something like frequency in MHz) or we need to change limit in DB for sensor_value.

      Attachments

        Issue Links

          Activity

            [OBS-3663] New classes request

            distance was added in r11079.
            (frequency issue will fixed soon, not related to this issue)

            landy Mike Stupalov added a comment - distance was added in r11079. (frequency issue will fixed soon, not related to this issue)
            • frequency - already exist (for years);
            • bitrate - is not sensor, use graphs, or as temporary way - gauge sensor class;
            • distance - will added soon.
            landy Mike Stupalov added a comment - frequency - already exist (for years); bitrate - is not sensor, use graphs, or as temporary way - gauge sensor class; distance - will added soon.

            I think there is no need for snmp dump.
            Или уточните какой именно дамп требуется.

            mtivi Martyushev Tim added a comment - I think there is no need for snmp dump. Или уточните какой именно дамп требуется.

            Please make and attach additional information about the device:

            • full snmp dump from device:

              snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
              snmpwalk -v2c -c <community>  --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> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --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
              mtivi Martyushev Tim
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: