On Fri, 17 Dec 2021 13:08:58 +0100 (CET) "FOUR Ludovic (EXT)" ludovic.four@unistra.fr wrote:

Hi Morten,

Thanks for the reply. I know how to use SNMP OID's but I must admit i'm not really comfortable yet with MIB schemas. I've learned something with OBJECT IDENTIFIER and ::= { enterprises } in the MIB file today ! Thanks a lot ! :)

No problem :)

I can check SNMP connectivity in seedDB IP devices but there's still nothing in collected info Type Found no new type in SeedDB (unknown empty)

If I remove one of the devices from Seed Database, and add it again but nothing happens. Still no sensor graph

The ipdevpoll `inventory` job needs to run successfully for the device to be identified first (and, unfortunately, the sensor may not be added on the first inventory run. The first run sets the device type, so that the sensors plugin has that value available only on the second run - and by default, successful runs are on 6 hour intervals).

You should see all succesful/failing jobs in the job status box in the ipdevinfo page of your sensor device (just search for it in the navbar). If the jobs aren't running at all, are you sure ipdevpoll is running?

You can also run these jobs manually from the command line:

ipdevpolld -J inventory -n <name-of-sensor-device>

Run it twice, and see if the sensor appears in ipdevinfo. Once it does, the 1minstats plugin should collect data from the registered sensors every 60 seconds.

Another point with serverscheck sensor : if I use snmpwalk to interrogate my sensor temperature, i get this : iso.3.6.1.4.1.17095.3.2.0 = STRING: "22.07"

It appears that the sensor value format is STRING, not as integer. Is that a problem ?

I think it should be fine; as long as you do not provide a precision value in the sensor record, the string would be sent raw to Graphite. SNMP doesn't really have a data type for floating point numbers, so there are usually only two ways to go about this: Use strings, or provide a scaled value.