SNMP is reporting trap is report a value as infinity which is not valid json

[thel1988]

We have been testing sc4snmp for a while now, we have seen if a device is report values as infinty eg:
memoryDeviceSerialNumberName": Infinity or "fruSerialNumberName": Infinity it will cause both the Otel collector and splunk enterprise to not parse it as valid json.

from the JSON spec:
Infinity is not a valid value in the official JSON specification (RFC 8259). While it's a recognized special numeric value in languages like Python and JavaScript, a compliant JSON parser must reject it. The value should be represented as null (if it's unknown or not applicable) or as a quoted string "Infinity"

Is it possible to overwrite the infinity values with quotes when returned in both snmp traps and snmp walks?

Both a Splunk HEC and a Splunk HEC endpoint hosted on a otel collector is rejecting the events as they should?

[omrozowicz-splunk]

Hey @thel1988, Can you show us the snippet of how this fruSerialNumberName and/or memoryDeviceSerialNumberName value look when it is retrieved by the bare snmpget?

We’ll take this into account while planning the work for the upcoming sprints.

[thel1988]

Yes ofcause I can

But they return about the same value:

IDRAC-MIB-SMIv2::fruSerialNumberName.1.8 = STRING: "2606123B"
IDRAC-MIB-SMIv2::fruSerialNumberName.1.9 = STRING: "2605C123"

IDRAC-MIB-SMIv2::memoryDeviceSerialNumberName.1.8 = STRING: "2605F3D0"
IDRAC-MIB-SMIv2::memoryDeviceSerialNumberName.1.9 = STRING: "2605F123"

No value is out of the ordinary. The weird thing is that, it seems to be only one specific host. Cant really see why it would get the value infinity instead of the serial

[omrozowicz-splunk]

Okay, I think know what can be the issue here. Are the hosts returning that Infinity value by any chance returning the strings with only numbers and "E" letters? because we check the type with this function:

def value_as_best(value) -> Union[str, float]:
    try:
        return float(value)
    except ValueError:
        return value
    except TypeError:
        return value

and when the string looks like this 2605F3D0 then it works as expected, but when it includes only E letters it treats it like a mathematical E notation. An example:

>>> float("2605F3D0")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: could not convert string to float: '2605F3D0'
>>> float("260E3100")
inf

This is probably what causes this bug. Can you take a look if this can be connected with your case? we'll dig in some more in the meanwhile.

[thel1988]

It seems it is the same which are causing this error with those strings:

IDRAC-MIB-SMIv2::memoryDeviceSerialNumberName.1.5 = STRING: "849867E3"
IDRAC-MIB-SMIv2::memoryDeviceSerialNumberName.1.6 = STRING: "84986806"
IDRAC-MIB-SMIv2::memoryDeviceSerialNumberName.1.7 = STRING: "849867E2"
IDRAC-MIB-SMIv2::memoryDeviceSerialNumberName.1.8 = STRING: "849867E9"

[omrozowicz-splunk]

Hello @thel1988,
the beta version with a fix was released within #1219. It is 1.13.0-beta.5. If you're okay with using beta versions you can upgrade it according to this doc and let us know if it solved the issue.