Werk #22399: SNMPv3 contexts: Allow querying the default context together with other contexts
| Component | Setup | ||||||
| Title | SNMPv3 contexts: Allow querying the default context together with other contexts | ||||||
| Date | Oct 2, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
The rule "SNMPv3 contexts to use in requests" could not include the default context (the empty context name). As soon as the rule named any context, Checkmk stopped querying the default context. Services found in the default context then vanished on the next service discovery.
The rule now has the option "Query the default context (no context name)".
It is enabled by default for new rules.
Existing rules keep their behavior: the option is disabled, unless the default context was already configured, e.g. in a rules.mk file.
The default context is always the first context of a rule.
If it was configured at a different position, e.g. in a rules.mk file, it is moved to the first position when the rule is saved or the site is updated.
This matters when several contexts return the same OIDs: only the data of the first context is used.
If you need such overlapping data from several contexts, create one host per context.
Via the REST API, the default context "" has to be given as the first context and only once, otherwise the rule is rejected as outdated value format.