You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dell iDRAC OIDs don't appear to be consistent as far as which value they provide if system model is different, iDRAC version is different, or even model is the same, but hardware config differs even slightly (1 CPU vs. 2 CPUs, 1 PSU vs. 2 PSUs, etc).
iDRAC provides OIDs that do describe the names of each value in each snmp table, which match the order of the actual data values displayed, so it's easy to figure out which value is which and manually change the OIDs in the telegraf config to match your setup.
A way to parse this information though and dynamically figure out the actual "description name" (i.e. "CPU 1 Temp") for each raw value OID provided would certainly make things easier. Not sure if this can be done in telegraf itself, maybe by polling entire snmp table rather than individual OIDs, however my knowledge in telegraf and this logic that needs to be created is lacking.
The text was updated successfully, but these errors were encountered:
Dell iDRAC OIDs don't appear to be consistent as far as which value they provide if system model is different, iDRAC version is different, or even model is the same, but hardware config differs even slightly (1 CPU vs. 2 CPUs, 1 PSU vs. 2 PSUs, etc).
iDRAC provides OIDs that do describe the names of each value in each snmp table, which match the order of the actual data values displayed, so it's easy to figure out which value is which and manually change the OIDs in the telegraf config to match your setup.
A way to parse this information though and dynamically figure out the actual "description name" (i.e. "CPU 1 Temp") for each raw value OID provided would certainly make things easier. Not sure if this can be done in telegraf itself, maybe by polling entire snmp table rather than individual OIDs, however my knowledge in telegraf and this logic that needs to be created is lacking.
The text was updated successfully, but these errors were encountered: