Werk #22672: REST API: Notification rules reject host tag conditions without tags
| Component | REST API | ||||
| Title | REST API: Notification rules reject host tag conditions without tags | ||||
| Date | Nov 12, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Incompatible - Manual interaction might be required | ||||
| Checkmk versions & editions |
|
When creating or editing a notification rule through the REST API, an entry of match_host_tags with tag_type set to tag_group was accepted without the tags to match:
- without
tag_idfor the operatorsisandis_not - without
tag_idsfor the operatorsone_ofandnone_of
Such an entry was dropped without notice. The rule was stored without this host tag condition, so it matched more hosts than intended.
The REST API now rejects such requests with status code 400 and names the missing field.
This werk is incompatible: scripts that send such entries now fail.
Add tag_id or tag_ids to the entry, or remove the entry to keep the previous behavior.
Existing rules are not changed. Checkmk cannot tell which rules were created with such an entry, because the entry was not stored. If your scripts may have sent such requests, compare the host tag conditions of the rules they created with the conditions you intended, and add the missing ones.