[
https://issues.apache.org/jira/browse/FELIX-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478824#comment-17478824
]
Carsten Ziegeler commented on FELIX-6499:
-----------------------------------------
[~henzlerg] I think there are different use cases - now, first of all, I assume
that you usually either inspect the endpoints or have some eventing/alerting
mechanism to react to the state. In that case, logging is only useful as an
additional debugging mechanism to find out later on why something was not OK.
For those cases, info logging is enough, as a warn log message creates
potentially to much noise. And yes, those might end up in additional alerts
For a system that purely relies on log messages, logging in INFO/WARN is fine
With FELIX-6480 we lost the option to have INFO log output of state changes
> Add option to monitor service to always log with info level
> -----------------------------------------------------------
>
> Key: FELIX-6499
> URL: https://issues.apache.org/jira/browse/FELIX-6499
> Project: Felix
> Issue Type: Improvement
> Components: Health Checks
> Affects Versions: healthcheck.core 2.0.12
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: healthcheck.core 2.0.14
>
>
> When the option "logResult" is enabled, msgs are either logged with INFO
> (state==OK) or WARN (state!=OK).
> We should add an option to always log with INFO level
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
