Werk #22194: SNMP section rule sets: matching rules no longer shown as overridden
| Component | Setup | ||||
| Title | SNMP section rule sets: matching rules no longer shown as overridden | ||||
| Date | Oct 22, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
Previously, the rule sets Disabled or enabled sections (SNMP), Fetch intervals for SNMP sections and SNMPv3 contexts to use in requests showed only the first matching rule as applying to a host. Every further matching rule was marked with "This rule matches, but is overridden by a previous rule", and the host's effective parameters listed only the first rule.
This did not reflect what Checkmk actually does: all matching rules of these rule sets apply, and for each SNMP section the first rule that covers it decides. A rule shown as overridden could therefore still disable a section or change its fetch interval or SNMPv3 contexts. For example, a general rule disabling a section still applied to a host even though a host-specific rule above it was shown as the one in effect, simply because that rule did not list the section.
The rule lists and effective parameters now show all matching rules as applying, and the help of each rule set explains which rule wins for a section.
One case did not follow this rule: in Fetch intervals for SNMP sections, a rule set to "Fetch data every time" did not override an interval that a lower rule configured for the same section. It now does, so such sections are fetched at every check from now on. Apart from that, how your SNMP hosts are monitored does not change.
If a higher-priority rule should override a lower one for a particular section, list that section in the higher rule explicitly, for example under Enabled sections.