Nagios Support Forum

Hello,

I need to monitor a lot of log files with Nagios and I came across the check_logfiles plug-in. One of the features that we need is to be able to reset the status of the service defined in Nagios to "OK", from
the Nagios GUI, once we fixed the issue.
I am able to keep the status for a defined period of time (with sticky option) but, once the issue is fixed, It is better (in my opinion) to switch the status to OK so that we can clearly see if other patterns are detected into the log file.
Sending a Passive check does not help as the service become critical on the next check.

On the other side, if the sticky option is not used the service will become OK on the next check .. so there is a risk not to see the critical alert.

It seems that the only thing that can be done is to send a specific message to the same log file in order to change the service status to OK. But how can this be done from the NAGIOS GUI on demand?

Did someone succeed in doing this? I saw a similar question posted some time ago but it seems that nobody answered to it.

Could you please share with me some of the best practices in monitoring log files with Nagios?


Regards,
Costel

Not quite sure what you are asking here, if you are trying to change the status to OK and it flips back to critical that should indicate you did not actually fix the problem correct?

Hello,

In fact the question is how to fit the log files events into the Nagios way of monitoring.

If a service is down and the next check the service is up we can say the issue is fixed.
With the log monitoring, If a pattern appear in a log file and the next check there is no new pattern appearing again, it does not mean that the issue is fixed.
I am trying to find out how to translate this logic in Nagios.

Regards,
C

This is already being discussed in your original thread, locking this one.