You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by oa...@apache.org on 2019/11/20 13:52:17 UTC
[camel] branch master updated: CAMEL-14187: Fix asciidoc warnings
related to the inline reference
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/56280e5032c88aeb3b0558e148f42ef681bf169a
The following commit(s) were added to refs/heads/master by this push:
new 56280e5 CAMEL-14187: Fix asciidoc warnings related to the inline reference
new aee5ec1 Merge pull request #3352 from omarsmak/CAMEL-14187
56280e5 is described below
commit 56280e5032c88aeb3b0558e148f42ef681bf169a
Author: Omar Al-Safi <om...@gmail.com>
AuthorDate: Wed Nov 20 14:49:27 2019 +0100
CAMEL-14187: Fix asciidoc warnings related to the inline reference
---
.../src/main/docs/metrics-component.adoc | 28 ++++++++++++----------
.../src/main/docs/micrometer-component.adoc | 12 ++++++----
2 files changed, 24 insertions(+), 16 deletions(-)
diff --git a/components/camel-metrics/src/main/docs/metrics-component.adoc b/components/camel-metrics/src/main/docs/metrics-component.adoc
index c8790a1..d4712fc 100644
--- a/components/camel-metrics/src/main/docs/metrics-component.adoc
+++ b/components/camel-metrics/src/main/docs/metrics-component.adoc
@@ -126,7 +126,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.
@@ -213,7 +214,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]
----
@@ -231,7 +233,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]
----
@@ -288,7 +290,8 @@ from("direct:in")
----
-== [[MetricsComponent-histogram]]Metric type histogram
+[[MetricsComponent-histogram]]
+== Metric type histogram
[source]
----
@@ -344,7 +347,8 @@ from("direct:in")
----
-== [[MetricsComponent-meter]]Metric type meter
+[[MetricsComponent-meter]]
+== Metric type meter
[source]
----
@@ -397,7 +401,8 @@ from("direct:in")
.to("direct:out");
----
-== [[MetricsComponent-timer]]Metrics type timer
+[[MetricsComponent-timer]]
+== Metrics type timer
[source]
----
@@ -450,7 +455,8 @@ from("direct:in")
.to("direct:out");
----
-== [[MetricsComponent-gauge]]Metric type gauge
+[[MetricsComponent-gauge]]
+== Metric type gauge
[source]
----
@@ -501,7 +507,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
@@ -558,7 +564,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
@@ -582,7 +588,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:
@@ -657,5 +663,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/components/camel-micrometer/src/main/docs/micrometer-component.adoc b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
index 88a0d92..6ea9ab6 100644
--- a/components/camel-micrometer/src/main/docs/micrometer-component.adoc
+++ b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
@@ -128,7 +128,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.
@@ -226,7 +227,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]
----
@@ -304,7 +306,8 @@ from("direct:in")
----
-== [[MicrometerComponent-summary]]Distribution Summary
+[[MicrometerComponent-summary]]
+== Distribution Summary
[source]
----
@@ -372,7 +375,8 @@ from("direct:in")
----
-== [[MicrometerComponent-timer]]Timer
+[[MicrometerComponent-timer]]
+== Timer
[source]
----