Title: apc_symmetra: “runtime” metric scaled wrong in graph since 2.5.0 (factor 60)
Edition/Version: Checkmk 2.5.0 (please complete with your edition: CRE/CEE/CCE)
Affected check: apc_symmetra (APC Symmetra Status)
Devices: 2x APC UPS (please add exact model + NMC firmware version)
Summary
After the update to 2.5.0 the runtime value reported by apc_symmetra is rendered correctly in the service summary but is off by a factor of 60 in the graph (“Verbleibende Lebenszeit” / remaining lifetime). The raw perfdata value is treated as seconds in the summary but apparently as minutes in the metric definition used for the graph.
Service output
Battery status: normal, No battery needs replacing,
Output status: on line (calibration invalid),
delay after calibration: 99.00,
Capacity: 99.00%,
Time remaining: 1 hour 1 minute
Perfdata (source code)
capacity=99;;;0;100 runtime=3629;;;;
Graph value (Verbleibende Lebenszeit)
2 d 11 h 2 d 14 h 2 d 13 h 2 d 13 h
Math
3629 s= 1 h 0 min 29 s → matches the summary (“1 hour 1 minute”)3629 min= 60 h 29 min ≈ 2 d 12 h → matches the graph
So the same raw perfdata number is interpreted as seconds by the check’s summary renderer and as minutes by the metric definition that feeds the graph.
SNMP raw value
(Please add the output of:
snmpwalk -v2c -c <community> <ups-ip> .1.3.6.1.4.1.318.1.1.1.2.2.3.0
so the Checkmk team can see whether the NMC returns Timeticks or an INTEGER, and which unit.)
Expected behaviour
Graph and summary use the same unit for runtime. Based on the summary rendering, the perfdata value is seconds, so the metric definition should be Unit(TimeNotation()) with Magnitude.SECOND.
Observed behaviour
Graph shows runtime × 60 (i.e. interprets the seconds value as minutes).
Workarounds tested so far
- None applied yet on the production system. Summary is correct, so service state and notifications are unaffected — only the historic graph is wrong.
Question to the community / devs
- Is there already a Werk for this in 2.5.0p* that I missed?
- Anyone else seeing this on APC UPS after the 2.5 upgrade?
Thanks!