[camel] branch master updated: regen docs

[oa...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

oalsafi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


View the commit online:
https://github.com/apache/camel/commit/8b959917e78250d189b465eb2e4edff0616de548

The following commit(s) were added to refs/heads/master by this push:
     new 8b95991  regen docs
8b95991 is described below

commit 8b959917e78250d189b465eb2e4edff0616de548
Author: Omar Al-Safi <om...@gmail.com>
AuthorDate: Wed Nov 20 14:58:39 2019 +0100

    regen docs
---
 .../modules/ROOT/pages/metrics-component.adoc      | 28 ++++++++++++----------
 .../modules/ROOT/pages/micrometer-component.adoc   | 12 ++++++----
 2 files changed, 24 insertions(+), 16 deletions(-)

diff --git a/docs/components/modules/ROOT/pages/metrics-component.adoc b/docs/components/modules/ROOT/pages/metrics-component.adoc
index 1cb1c99..1c9fcf0 100644
--- a/docs/components/modules/ROOT/pages/metrics-component.adoc
+++ b/docs/components/modules/ROOT/pages/metrics-component.adoc
@@ -127,7 +127,8 @@ The component supports 5 options, which are listed below.
 
 
 
-== [[MetricsComponent-registry]]Metric Registry
+[[MetricsComponent-registry]]
+== Metric Registry
 
 Camel Metrics component uses by default a `MetricRegistry` instance with
 a `Slf4jReporter` that has a 60 second reporting interval.
@@ -214,7 +215,8 @@ endpoint finishes processing of exchange. While processing exchange
 Metrics endpoint will catch all exceptions and write log entry using
 level `warn`.
 
-== [[MetricsComponent-counter]]Metrics type counter
+[[MetricsComponent-counter]]
+== Metrics type counter
 
 [source]
 ----
@@ -232,7 +234,7 @@ metrics:counter:metricname[?options]
 
 If neither `increment` or `decrement` is defined then counter value will
 be incremented by one. If `increment` and `decrement` are both defined
-only increment operation is called. 
+only increment operation is called.
 
 [source,java]
 ----
@@ -289,7 +291,8 @@ from("direct:in")
 
 ----
 
-== [[MetricsComponent-histogram]]Metric type histogram
+[[MetricsComponent-histogram]]
+== Metric type histogram
 
 [source]
 ----
@@ -345,7 +348,8 @@ from("direct:in")
 
 ----
 
-== [[MetricsComponent-meter]]Metric type meter
+[[MetricsComponent-meter]]
+== Metric type meter
 
 [source]
 ----
@@ -398,7 +402,8 @@ from("direct:in")
     .to("direct:out");
 ----
 
-== [[MetricsComponent-timer]]Metrics type timer
+[[MetricsComponent-timer]]
+== Metrics type timer
 
 [source]
 ----
@@ -451,7 +456,8 @@ from("direct:in")
     .to("direct:out");
 ----
 
-== [[MetricsComponent-gauge]]Metric type gauge
+[[MetricsComponent-gauge]]
+== Metric type gauge
 
 [source]
 ----
@@ -502,7 +508,7 @@ from("direct:in")
 This factory allows to add a RoutePolicy for each
 route which exposes route utilization statistics using Dropwizard metrics.
 This factory can be used in Java and XML as the examples below
-demonstrates. 
+demonstrates.
 
 NOTE: Instead of using the MetricsRoutePolicyFactory you can define a
 MetricsRoutePolicy per route you want to instrument, in case you only
@@ -559,7 +565,7 @@ value. Where `###name###` is the name of the CamelContext. `###routeId###`
 is the name of the route. And `###type###` is the value of responses.
 |=======================================================================
 
- 
+
 
 From Java code you can get hold of
 the `com.codahale.metrics.MetricRegistry` from the
@@ -583,7 +589,7 @@ This factory allows to use metrics to
 capture Message History performance
 statistics while routing messages. It works by using a metrics Timer for
 each node in all the routes. This factory can be used in Java and XML as
-the examples below demonstrates. 
+the examples below demonstrates.
 
 From Java you just set the factory to the `CamelContext` as shown below:
 
@@ -658,5 +664,3 @@ with `name=MetricsMessageHistoryService`.
 This factory allows you to gather performance information about Camel Thread Pools by injecting a InstrumentedThreadPoolFactory
 which collects information from inside of Camel.
 See more details at Advanced configuration of CamelContext using Spring
-
-
diff --git a/docs/components/modules/ROOT/pages/micrometer-component.adoc b/docs/components/modules/ROOT/pages/micrometer-component.adoc
index 10bc6c5..e1500c4 100644
--- a/docs/components/modules/ROOT/pages/micrometer-component.adoc
+++ b/docs/components/modules/ROOT/pages/micrometer-component.adoc
@@ -129,7 +129,8 @@ The component supports 5 options, which are listed below.
 
 
 
-== [[MicrometerComponent-registry]]Meter Registry
+[[MicrometerComponent-registry]]
+== Meter Registry
 
 By default the Camel Micrometer component creates a `SimpleMeterRegistry` instance, suitable
 mainly for testing.
@@ -227,7 +228,8 @@ All Metrics specific headers are removed from the message once the Micrometer en
 Micrometer endpoint will catch all exceptions and write log entry using level `warn`.
 
 
-== [[MicrometerComponent-counter]]Counter
+[[MicrometerComponent-counter]]
+== Counter
 
 [source]
 ----
@@ -305,7 +307,8 @@ from("direct:in")
 
 ----
 
-== [[MicrometerComponent-summary]]Distribution Summary
+[[MicrometerComponent-summary]]
+== Distribution Summary
 
 [source]
 ----
@@ -373,7 +376,8 @@ from("direct:in")
 ----
 
 
-== [[MicrometerComponent-timer]]Timer
+[[MicrometerComponent-timer]]
+== Timer
 
 [source]
 ----