Details

    • New Feature
    • Resolution: Unresolved
    • Major
    • None
    • Professional Edition
    • Poller

    Description

      I found ticket OBS-2336 bit it seems to be dead since 2017. Because we need for various reasons some of the data observium collects in different metrics I checked the existing influxdb integration.

      The first thing I saw that it is not compatible with influxdb 2.x because it is just using - of course - the first API. And of course it is very basic.

       

      I reworked it a bit so it is working with API2, too. Is it possible the patch appended into source code?

       

      Next: Because it is using curl in a very basic way, would it possible to integrate the official influxdb-php API into observium? (https://github.com/influxdata/influxdb-client-php) May be as some kind of plugin?

      Not sure how often it is used that data collected from observium are exported to influxdb, but for us this is a really really usefull ability.

      Attachments

        Issue Links

          Activity

            [OBS-4243] Extend existing influxdb integration

            I asked for this one and a half year ago meanwhile - so ping - is it possible to integrate this? This integration helps us lot to make some different visualisation on metrics of hundreds of devices.

            albrecht Rajko Albrecht added a comment - I asked for this one and a half year ago meanwhile - so ping - is it possible to integrate this? This integration helps us lot to make some different visualisation on metrics of hundreds of devices.

            It is not about any problems with snmp or discover or polling or a problem with a device.

            albrecht Rajko Albrecht added a comment - It is not about any problems with snmp or discover or polling or a problem with a device.

            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 -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

            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 -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 This comment is added automatically.

            People

              landy Mike Stupalov
              albrecht Rajko Albrecht
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: