You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (JIRA)" <ji...@apache.org> on 2015/11/25 08:57:11 UTC
[jira] [Assigned] (CAMEL-9342) Metrics component should log at
debug level
[ https://issues.apache.org/jira/browse/CAMEL-9342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Cosentino reassigned CAMEL-9342:
---------------------------------------
Assignee: Andrea Cosentino
> 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.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)