Werk #22165: Check_MK Agent: Host name mismatch with agent updater no longer CRIT
| Component | Checks & agents | ||||
| Title | Check_MK Agent: Host name mismatch with agent updater no longer CRIT | ||||
| Date | Sep 30, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
Since Werk #15358, the service Check_MK Agent has compared two host names.
The first is the host name under which the agent updater is registered.
The second is the name of the host in Checkmk.
A difference between the two sent the service to CRIT.
This comparison caused false alarms. A host can be monitored by several sites, and each site may know the host under a different name. The agent updater, however, is registered with one site only. All other sites therefore reported a mismatch, although they have nothing to do with agent updates.
The ruleset Checkmk agent installation auditing now has the option State in case of host name mismatch with the agent updater.
This option defaults to WARN.
Previously, a mismatch always resulted in CRIT.
On sites that monitor a host without serving its agent updates, set this option to OK.
The service then shows the mismatch only in its details, next to the host name used by the agent updater.
If you want the previous behavior back, set the option to CRIT.