Matching criteria
Text to Match: [my_criteria]
Match host: [my_host] Outcome & Action
Rule type: Normal Operation
State: CRIT Counting & Timing
Expect regular messages: 1 msg per day
But for the matching criteria it will generate a CRIT state even if messages are received within the expected time frame.
Fortunately, the Events service for those hosts seems unaware of these Event Console events, so the service state stays OK (as I want it, since regular messages were received during the set time limit)
But the strange thing is that the Event console is actually generating unexpected CRIT states:
What’s your criteria? You need to detect the exact match of the incomming message. If something different, the rule will not work. You can work with matchin groups to create an uniqe key. Use mathing groups on the dynamic informations.
(a very minor issue is that to have the host field correctly populated for this event I had to enable “Rewrite host name” in the rule, otherwise it’s empty)
Now the remaining issue is the behavior of this rule when the expected messages ARE received within the set time limit: see next post.
Why is checkmk creating a CRIT event at all and how can the target count be not reached yet if I sent 4 messaged very rapidly while the rule is expecting 1 message per 5 minutes?
