Werk #22318: Fix bulk notifications failing with long host or service names
| Component | Notifications | ||
| Title | Fix bulk notifications failing with long host or service names | ||
| Date | Oct 1, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
Previously, bulk notifications failed when the values used to separate the bulks were too long. This happened with long host or service names, or when many options were selected under Create separate bulk notifications based on. Checkmk stores each bulk in a directory named after these values, and once that name exceeded 255 bytes, the notification could not be stored and was never sent.
Such bulks now get a directory name based on a hash of these values. Notifications with the same values still end up in the same bulk, and the Open bulk notifications table still shows the readable bulk ID.
A notification that cannot be stored for bulk sending for other reasons,
for example missing permissions in var/check_mk/notify/bulk, is not sent.
Checkmk logs the error in var/log/notify.log and lists the notification
under Failed notifications, so you can fix the cause.