Werk #19827: Fix Event Console self-monitoring with syslog or SNMP trap enabled
| Component | Checks & agents | ||||||
| Title | Fix Event Console self-monitoring with syslog or SNMP trap enabled | ||||||
| Date | Jun 12, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Incompatible - Manual interaction might be required | ||||||
| Checkmk versions & editions |
|
The shipped rule for the ruleset Process discovery that monitors the Event
Console process of a Checkmk server reported CRIT whenever one of the Event
Console's built-in receivers (syslog, syslog via TCP, or SNMP traps) was enabled.
When such a receiver is active, the Event Console process is started with
additional command-line arguments (for example --snmptrap). The shipped rule
matched the process command line too strictly and did not expect these extra
arguments, so the process was no longer recognized and its monitoring service
went CRIT.
The shipped rule now matches the Event Console process regardless of which built-in receivers are enabled. During an update, Checkmk corrects the affected rule automatically.
Incompatibility hint
This automatic correction only applies if you did not change the rule yourself. If you have manually adapted the process matching pattern of this rule, it is left untouched, and you have to adjust the pattern yourself so that it also matches the additional command-line arguments.
Suggested adaptation:
~python3 /omd/sites/[^/]+/bin/mkeventd$
should become
~python3 /omd/sites/[^/]+/bin/mkeventd(.*)?$