Werk #19964: InfluxDB metric forwarding: fixed handling of one-sided or unbounded thresholds
| Component | The Checkmk Micro Core | ||
| Title | InfluxDB metric forwarding: fixed handling of one-sided or unbounded thresholds | ||
| Date | Jun 12, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
When the Send metrics to InfluxDB rule is configured with Thresholds
enabled under Additional values per metric, thresholds for certain
services were not forwarded correctly to InfluxDB. This affected
services whose performance data thresholds contained inf or -inf,
which Checkmk uses internally to represent "no bound".
The most common scenario is services monitored via the Local checks mechanism where the check script only specifies a warning threshold without a corresponding critical threshold (or vice versa). In that case, Checkmk fills in the missing bound with infinity.
Additionally, services monitored by the following built-in check plugins were also affected, as they explicitly use infinity to represent one-sided thresholds:
- Rittal CMC / CMC III (Computer Multi Control) — temperature, LCP, and waterflow monitoring
- Oracle database — recovery status monitoring
CMC's InfluxDB metric forwarding now treats inf as "no upper bound"
and -inf as "no lower bound", matching the intended semantics. No
configuration changes are required.