[
https://issues.apache.org/jira/browse/CAMEL-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477318#comment-16477318
]
christian ohr commented on CAMEL-11600:
---------------------------------------
Started off as a copy of camel-metrics, but the details of the underlying
metrics libraries caused differences:
* Micrometer is dimensional (name + key/value tags) while metrics is
hierarchical (names). As such, the strategy for finding suitable names is
different/easier because all meta data related to routes or exchanges can be
stored as a tag. NamingStrategy interfaces (with default instances) were added
to derive custom names/tags for meters.
* Micrometer has no concept of reporters, instead, metric destinations are
part of the registry implementation. So, in order to publish Camel metrics to
JMX, you have to have a CompositeMeterRegistry with a JmxMeterRegistry added.
* Micrometer Gauges follow the observer pattern, i.e. in general they observe
another value rather than setting it explicitly. Therefore, for the time being
there is no Gauge producer like in camel-metrics.
* Micrometer Timers and DistributionSummaries (histograms) do not publish
rates, fixed percentiles etc. out of the box. This is configurable for each
meter or by means of a DistributionStatisticConfig, but also depends on the
monitoring destination (e.g. Prometheus prefers to calculate derived statistics
itself, while most others require the client to deliver these statistics)
In addition to camel-metrics:
* There are also EventNotifiers.
* Meter names and tags as well as some producer parameters are evaluated as
Simple language expressions (e.g. "to(micrometer:counter:${header.myName}")
* There is a camel-example-micrometer example module that demonstrates some
simple routes throwing statistics at a Prometheus backend.
> camel-micrometer - Add support for micrometer for metrics capture
> -----------------------------------------------------------------
>
> Key: CAMEL-11600
> URL: https://issues.apache.org/jira/browse/CAMEL-11600
> Project: Camel
> Issue Type: New Feature
> Reporter: Claus Ibsen
> Priority: Major
>
> Look at using http://micrometer.io/
> We can do something similar to camel-metrics which uses the dropwizard
> library.
> Then we can make it pluggable so it can be setup to do timings of Camel
> routes how long time it takes to process exchanges and so on.
> We can possible make it as plugable as you just add camel-micrometer on the
> classpath and its auto enabled. Like we do for camel-fastermap etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
