toni-moreno
commented
2 years ago Hello @matejv , I've reviewed the RFC where is defined this snmp type here ( https://datatracker.ietf.org/doc/html/rfc2578#section-7.1.7)
7.1.7. Gauge32
The Gauge32 type represents a non-negative integer, which may
increase or decrease, but shall never exceed a maximum value, nor
fall below a minimum value. The maximum value can not be greater
than 2^32-1 (4294967295 decimal), and the minimum value can not be
smaller than 0. The value of a Gauge32 has its maximum value
whenever the information being modeled is greater than or equal to
its maximum value, and has its minimum value whenever the information
being modeled is smaller than or equal to its minimum value. If the
information being modeled subsequently decreases below (increases
above) the maximum (minimum) value, the Gauge32 also decreases
(increases). (Note that despite of the use of the term "latched" in
the original definition of this type, it does not become "stuck" at
its maximum or minimum value.)As you can read 4294967295 is 2^32-1 and a valid value , you should also note that Gauge32 represents a non-negative integer . ( 32 bits) so it seems like it can never be -1
regarding this information snmpcollector seems to be returning the correct value.
matejv
Hello
I have a device, which returns all data as Gauge32. There is an OID that should be interpreted as an signed 32bit integer.
The value 4294967295 is actually 2^32 or if taken as a signed int32 it will be -1. -1 is the value I need.
When I set-up SNMP Metric, I selected for
DataSrcTypeall possible integer values. No matter what I select I always get 4294967295 as a result by snmpcollector.Does
DataSrcTypenot force casting values as selected type? It seems to me that snmpcollector respects what type the data is as returned via SNMP no matter what (so gauge32 in my case).Debug for problematic device log bellow:
I'm running version 0.12.0. I also tested on 0.10.0 with the same results.
Attaching my configuration as well: bulkexport_20211221_1614.txt