[
https://issues.apache.org/jira/browse/CAMEL-9616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152416#comment-15152416
]
ASF GitHub Bot commented on CAMEL-9616:
---------------------------------------
GitHub user astefanutti opened a pull request:
https://github.com/apache/camel/pull/846
CAMEL-9616: Support looking up MetricRegistry by type only in the Metrics
component
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/astefanutti/camel CAMEL-9616
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/846.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #846
----
commit f00a64975e9a36323969961e57809743d53ffcb3
Author: Antonin Stefanutti <[email protected]>
Date: 2016-02-18T14:57:07Z
CAMEL-9616: Support looking up MetricRegistry by type only in the Metrics
component
commit 8a0f5b8526a8f67c79c75180a9ca7f2f04a4d068
Author: Antonin Stefanutti <[email protected]>
Date: 2016-02-18T14:58:59Z
Custom MetricRegistry bean has become unecessary given CAMEL-9616
----
> Support looking up MetricRegistry by type only in the Metrics component
> -----------------------------------------------------------------------
>
> Key: CAMEL-9616
> URL: https://issues.apache.org/jira/browse/CAMEL-9616
> Project: Camel
> Issue Type: Improvement
> Components: camel-metrics
> Reporter: Antonin Stefanutti
> Assignee: Antonin Stefanutti
> Priority: Minor
> Fix For: 2.17.0
>
>
> For the moment, a custom {{MetricRegistry}} bean can be provided but must be
> named. It would be easier to relax that constraint in case only one
> {{MetricRegistry}} bean exist and do the lookup by type only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
