anchor.diff:  [[MetricsComponent-registry]]Metric Registry
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   
  -Camel Metrics Component uses by default `MetricRegistry` with
  +Camel Metrics component uses by default `MetricRegistry` with
   `Slf4jReporter` and 60 second reporting interval. Default registry can
   be replaced with custom one by providing bean with name `metricRegistry`
   in Camel registry. For example using Spring Java Configuration.
  
positive.code: The **metrics:** component allows to collect various metrics directly
  from Camel routes. Supported metric types
  are link:#MetricsComponent-counter[counter], link:#MetricsComponent-histogram[histogram],
  link:#MetricsComponent-meter[meter] and link:#MetricsComponent-timer[timer]. http://metrics.codahale.com/[Metrics] provides
  simple way to measure behaviour of application. Configurable
  reporting backend is enabling different integration options for
  collecting and visualizing statistics. The component also provides
  a `MetricsRoutePolicyFactory` which allows to expose route statistics
  using codehale metrics, see bottom of page for details.
  
  Maven users will need to add the following dependency to their `pom.xml`
  for this component:
  
negative.code: ----
  
  CAUTION: `MetricRegistry` uses internal thread(s) for reporting. There is no
  public API in version `3.0.1` for users to clean up on exit. Thus using
  Camel Metrics Component leads to Java classloader leak and my cause
  `OutOfMemoryErrors` in some cases.
  
  