Event History State and Value Changes

3 votes

For local checks, CheckMK monitors based on state changes of a Service and we get an event history as this happens.

As part of any Fault finding the sequence of events is quite important along with the values of other services through Data Analytics. More often than not the service that went CRIT is usually the end product of other events and it would be great to know the status and values of other services in the period prior to the CRIT.

I'm proposing adding a capability (OFF by default) that an individual Service can be configured to generate more low level event history based on either a state change or a change in value of the service.

See attached example.

In the current system we only get 1 record to indicate Room temp went from OK to CRIT. We don't get the history of cooling to see that it didn't come on because its State was always OK.

Not planned Checks&Agents Suggested by: Ray Donohoe Upvoted: 07 Jan, '23 Comments: 4

Comments: 4