Daniel, I may be misunderstanding this (the docs on volatile are extremely light), but I don't see how that helps... A service that goes into CRITICAL state because of an error log would be passive only (I think) - something like logstash with its nagios_nsca plugin - what does volatile mean for passive-only service?
To recapitulate, I'm looking for a meaningful transition back to OK state for a passive-only service that becomes critical because of an application error log. There isn't an application-generated log that expresses a return to OK state (since application logs are generally about events and not about state transitions). So I guess I'm looking for some way for an *operator* to acknowledge that an error log has investigated and the service should go back to OK - it's pretty much a GUI question. Or if someone has a different approach to managing states with regards to application log events... Shay On Fri, Jun 19, 2015 at 8:16 AM, Daniel Parthey <[email protected]> wrote: > You might have a look at "volatile services". > > > http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/advanced-topics#volatile-services > _______________________________________________ > icinga-users mailing list > [email protected] > https://lists.icinga.org/mailman/listinfo/icinga-users >
_______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
