Werk #2041: Notification Spooler can now handle incoming and outgoing persistent TCP connections
|Title||Notification Spooler can now handle incoming and outgoing persistent TCP connections|
|Date||Mar 4, 2015|
|Checkmk Editon||Checkmk Raw (CRE)|
|Compatibility||Incompatible - Manual interaction might be required|
The Check_MK Notification Spooler (mknotifyd) has completely been rewritten. It now:
- uses persistent TCP connections instead of connecting for each notifiction
- can use outgoing TCP connections for receiving notifictions
- can handle an arbitrary number of parallel connctions
- monitors connections with heart beats
- is being monitored by two new checks for the general state and for each connection
The global configuration for the spooler has changed. Your existing settings are still supported but have vanished from WATO. As soon as you create a new configuration that will override your legacy configuration.
The new checks that monitor the spooler require an update of the Check_MK Agent for Linux on the Check_MK server. It needs OMD based installaions paths. All spoolers will automatically be discovered. The new checks are mknotifyd and mknotifyd.connection.
The spooler write messages into var/log/mknotifyd.log. There are three log levels, which can be configured in the global settings of the spooler. We propose starting with the highest log level. Also a file var/log/mknotifyd.log is being written every 20 seconds. It shows the state of the spooler and its connections. This is being used for the monitoring of the spooler.
Note: To get the new mknotifyd running you need to reconfigure its global settings. Otherwise it will use the incompatible configuration of the previous version.To the list of all Werks