Skip to main content

Hello,

We want to use the event handler functionality to do “self correction”.

By default, a service exits downtime does not generate any events and therefore is not traced by the event handler functionality.
Indeed, a service in CRITICAL state which exits downtime does not generate a new event and therefore cannot be processed.
This is our problem, because this service in CRITICAL state needs to be solved!

Is it right?
How can we do?

I guess we are not the first to ask ourselves this question but I have not found a clear answer.
Thank you in advance for your answers.

Regards,
V. Bodin

up

Hi,

I too am interested in the problematic.

I guess there is no easy solution. I can see none apart of the event handler script which process the event to keep running and periodically check if the service still is in downtime. And if not, and the status still is not OK, then does what it has to, and only then exits. This unlucky isn’t something which is simple to implement.

Also, in some cases, the remediation action could take place while the service still is in downtime. If it solves the issue then the service will be OK for when the downtime will end. Not always a solution though, if the remediation action can’t be issued during the downtime for any reason.

Reply


Terms & ConditionsCookie settings