Werk #16766: mknotifyd: use site names in service description
| Component | Checks & agents | ||||||
| Title | mknotifyd: use site names in service description | ||||||
| Date | May 27, 2024 | ||||||
| Level | Prominent Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Incompatible - Manual interaction might be required | ||||||
| Checkmk versions & editions |
|
This update affects users monitoring the OMD Notify Connection services, regardless of whether the connection is encrypted.
Previously it was not possible to correctly monitor the Notification Spooler connection with TLS. For encrypted incoming connections, the IP address and port were unavailable because managed by stunnel using Unix sockets. Consequently, services for encrypted connections were named incorrectly and always displayed the IP address as 127.0.0.1.
To resolve this issue, we have updated the service naming. Now, the names of the involved sites will be shown in the format: OMD MySite Notification Spooler connection to MyRemoteSite.
Impact:
- Currently monitored services (e.g., those configured with unencrypted connections) will continue to work as usual.
- Upon rediscovery, new services will be discovered and will adopt the new naming convention. For this reason, this werk is flagged as incompatible
- To maintain service history, users can create a service description translation rule. This can be done in the configuration at: Setup > Agents > Access to agents > Translation of service descriptions. Use a regex or static string to map the old service names to the new ones.