Werk #22852: EC: host limits follow changed hosts
| Component | Event Console | ||
| Title | EC: host limits follow changed hosts | ||
| Date | Oct 23, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
Some events of the Event Console change their host after they were created. A rule with Count messages in interval but without Force separate events for different hosts counts the messages of all hosts in a single event, and so does a rule with Expect regular messages. That event gets the host of each message counted. Likewise, an event about missing expected messages gets its host rewritten again whenever it is merged with a further one, e.g. after you changed the Rewrite host name of its rule.
The host limit of the global setting Limit amount of current events, nevertheless, kept counting such an event for its previous host. As a consequence, the Event Console:
- logged an error with a traceback in
var/log/mkeventd.logwhen it removed such an event, e.g. when you archived it or when the interval of its expecting rule ended, unless it counted other events for the new host. Archiving several events at once stopped at such an event, and the housekeeping of the events skipped its remaining tasks until its next run. - counted one event too many for the previous host, and, after such an error, for the rule, too. With enough of these events, a host or rule limit took effect, although fewer events were open, so the Event Console dropped messages or opened overflow events.
- showed the wrong hosts as having reached their limit.
The host limit now counts such an event for the host it currently has.