camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Cosentino (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-9342) Metrics component should log at debug level
Date Wed, 25 Nov 2015 16:30:11 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-9342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrea Cosentino resolved CAMEL-9342.
-------------------------------------
    Resolution: Fixed

> Metrics component should log at debug level
> -------------------------------------------
>
>                 Key: CAMEL-9342
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9342
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-metrics
>            Reporter: James Netherton
>            Assignee: Andrea Cosentino
>            Priority: Minor
>             Fix For: 2.16.2, 2.17.0
>
>
> The metrics component does the following:
> {code}
>  final Slf4jReporter reporter = Slf4jReporter.forRegistry(registry)
>                 .outputTo(LOG)
>                 .convertRatesTo(TimeUnit.SECONDS)
>                 .convertDurationsTo(TimeUnit.MILLISECONDS)
>                 .build();
> {code}
> This results in quite a bit of noise in application log files, as some (not particularly
useful) log output is generated each time the metrics thread runs. It'd be better to force
the log level for this output to DEBUG.
> Adding something like the following should be sufficient:
> {code}
> .withLoggingLevel(Slf4jReporter.LoggingLevel.DEBUG)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message