Change of check interval on services

CMK version:Checkmk Raw Edition 2.4.0

Hello,
I’m experiencing a bug.
I’m trying to change the interval between two checks on my interfaces. So I created a rule in Setup > Services > Service monitoring rules > Normal check interval for service checks.
This rule has the condition “Service name begins with Interface.”

However, this rule still uses my initial time of 5 minutes and doesn’t take my new interval into account.

Capture d’écran 2025-06-04 200847

However, when I click on “Parameters for this service,” I see my modified time.
And when I click on “Normal check interval for service checks for host XXX and service ‘YYY,’”

I see my rule validated and the default rule set to “This rules matches, but is overridden by a previous rule.”

How can I resolve this issue?

Sincerely,

You might would like to use regex here, so somthing like
Interface*
might work for you.

You cannot change the check interval of services that get their data from the agent. These are technically passive checks and are updated whenever the agent gets queried.

3 Likes

Hello,
I’ve already tested it with Interface*, but it doesn’t change anything.

I forgot to mention that for the interfaces I need to monitor, I don’t use the agent; I’m using SNMP.

It’s the same, agent was meant broadly by me. SNMP also queries an agent and special agents are also affected.
Basically every check that does not come form its own Nagios plugin (active check).

2 Likes

You need to understand the order in which rules are evaluated:

  1. First all rules in the same folder the host is located in are looked at; the first matching rule (from top to bottom) wins.
  2. If no match was found, look in the parent folder; repeat search there like in 1.
  3. Repeat 2 recursively until you’re in the main folder
  4. If no rule matches anywhere in steps 1–3, use global settings/built-in defaults.

The order of rules matters. Like I wrote, the first matching rule wins.

Thanks, I understand better why my changes on my Nagios checks and not the others.

Please keep in mind that checkmk is doing it differently than how its done traditionally in Nagios. In plain Nagios each service was an active check and was scheduled independently from each other. Here you had the luxury to use individual timing settings for the scheduling of the check plugin but with the cost that it consumes huge resources and the more services you have the slower your monitoring.
The agent based checks in checkmk doing it in a different way. The service Check_MK is the only active check (as long as you didn’t configure additional active checks like check_http etc.) and this check fetches ALL data or all services from the agent (snmp or checkmk) or special agent. Then this data is ‘distributed’ to all services and evaluated by the check plugins which then update the state of the service as Robert mentioned.
So, in case you need to change the timing of a passive check you can do this only with the active Check_MK service and ALL other passive service are always also affected by this change.
Bonus hint: Dont forget to change the RRD step settings same way.

have fun with monitoring

Mike

3 Likes