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

using REST API GET commands to create a device graph

Details

    • New Feature
    • Resolution: Unresolved
    • Minor
    • None
    • None
    • Default
    • None

    Description

      Hello

       

      I am unable to find specific documentation, but is it possible to draw graphs in observium with the information I can get with REST API ?

      For example, I want to GET certain numberical value every 5minutes, is there possibility for observium to read the device name, value and timestamp out of the API call to create a graph? The only way for me to receive these values are with REST API commands

      Attachments

        Activity

          [OBS-4676] using REST API GET commands to create a device graph
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          kaupo@wavecom.ee Kaupo Ehtnurm added a comment -

          I understand that you added nsx-t edge and managers support, but this is only with SNMP and with almost 0 information.
          I am asking this question, because I intend to monitor NSX-T T0 and T1 gateways, but these can be monitored with REST API...

          kaupo@wavecom.ee Kaupo Ehtnurm added a comment - I understand that you added nsx-t edge and managers support, but this is only with SNMP and with almost 0 information. I am asking this question, because I intend to monitor NSX-T T0 and T1 gateways, but these can be monitored with REST API...
          bot Observium Bot made changes -
          Component/s New: Default [ 10900 ]
          bot Observium Bot made changes -
          Assignee Original: Adam Armstrong [ adama ] New: Mike Stupalov [ landy ]
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          kaupo@wavecom.ee Kaupo Ehtnurm created issue -
          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.

          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

            landy Mike Stupalov
            kaupo@wavecom.ee Kaupo Ehtnurm
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: