You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pc...@apache.org on 2023/08/04 06:58:33 UTC
[camel-website] branch main updated (1cd72695 -> dd7f976c)
This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git
from 1cd72695 Add release info for Camel Quarkus 3.0.0-RC2
new 67f9934a feat: Camel-k 2.0 Micrometer Metrics
new dd7f976c chore: fix example link in camel-k prometheus blog post
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../blog/2022/07/camel-k-monitoring-ops/index.md | 6 +--
.../blog/2023/08/camel-k-micrometer/featured.png | Bin 0 -> 40751 bytes
content/blog/2023/08/camel-k-micrometer/index.md | 59 +++++++++++++++++++++
3 files changed, 62 insertions(+), 3 deletions(-)
create mode 100644 content/blog/2023/08/camel-k-micrometer/featured.png
create mode 100644 content/blog/2023/08/camel-k-micrometer/index.md
[camel-website] 01/02: feat: Camel-k 2.0 Micrometer Metrics
Posted by pc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 67f9934a308d90acbd6c95fdd67ae56065c1cf42
Author: Gaelle Fournier <ga...@gmail.com>
AuthorDate: Mon Jul 17 10:13:15 2023 +0200
feat: Camel-k 2.0 Micrometer Metrics
---
.../blog/2022/07/camel-k-monitoring-ops/index.md | 2 +-
.../blog/2023/08/camel-k-micrometer/featured.png | Bin 0 -> 40751 bytes
content/blog/2023/08/camel-k-micrometer/index.md | 59 +++++++++++++++++++++
3 files changed, 60 insertions(+), 1 deletion(-)
diff --git a/content/blog/2022/07/camel-k-monitoring-ops/index.md b/content/blog/2022/07/camel-k-monitoring-ops/index.md
index e88cd0b3..509dd690 100644
--- a/content/blog/2022/07/camel-k-monitoring-ops/index.md
+++ b/content/blog/2022/07/camel-k-monitoring-ops/index.md
@@ -14,7 +14,7 @@ First of all let's start presenting the Apache Camel component that will make th
When the component is available, the Integration will expose a _/q/metrics_ endpoint and you can use it for monitoring purposes.
-## Prometheus stack
+## Prometheus stack
If you look at the endpoint you will quickly notice that the information are not thought to be read by humans. They are infact designed to work with some scraping tool whose goal is to read the information and aggregate the results.
diff --git a/content/blog/2023/08/camel-k-micrometer/featured.png b/content/blog/2023/08/camel-k-micrometer/featured.png
new file mode 100644
index 00000000..359a894e
Binary files /dev/null and b/content/blog/2023/08/camel-k-micrometer/featured.png differ
diff --git a/content/blog/2023/08/camel-k-micrometer/index.md b/content/blog/2023/08/camel-k-micrometer/index.md
new file mode 100644
index 00000000..f9ef5dcb
--- /dev/null
+++ b/content/blog/2023/08/camel-k-micrometer/index.md
@@ -0,0 +1,59 @@
+---
+title: "Camel K Observability: Micrometer Metrics"
+date: 2023-08-03
+draft: false
+authors: [gansheer]
+categories: ["Camel K", "Features", "Devops"]
+preview: "Camel K 2.0: What changes to expect about Integration Metrics"
+---
+
+
+We already explained how to take monitor your Integrations in the previous blog post about [monitoring](/blog/2022/07/camel-k-monitoring-ops/) operations on Camel K. The good news is there are only a few changes with the move to [Micrometer Metrics](https://micrometer.io/).
+
+## From Microprofile to Micrometer
+
+Camel K 2.0 was the occasion to move from one technology (Microprofile) to another (Micrometer) for the [Prometheus trait configuration](/camel-k/next/traits/prometheus.html) implementation.
+
+The reason is the deprecation notice from [Quarkus Microprile's implementation](https://quarkus.io/guides/smallrye-metrics) in favor of using [Micrometer Metrics](https://quarkus.io/guides/telemetry-micrometer). This decision follows a [long period of transition](https://quarkus.io/blog/micrometer-metrics/) from Quarkus project.
+
+This change brings some powerful improvments for your monitoring. Micrometer delivers more advanced features such as hierarchical meters and dimensional data models, while MicroProfile Metrics provides a simpler API with basic metric types such as counters and gauges. Additionaly, Micrometer provides a simple facade over the instrumentation clients for the most popular monitoring systems, letting any library provides its own metrics through it.
+
+## Camel framework changes expected in Micrometer
+
+Metrics are generated by two types of sources:
+* the libraries powered by Camel components
+* the Micrometer Camel component
+
+Since Micrometer provides a facade, the changes in the default metrics from the libraries powered by camel components will depend on what they expose.
+
+Before Camel K 2.0, the [default camel metrics](/components/3.21.x/microprofile-metrics-component.html#_default_camel_metrics) where provided by the camel Microprofile Metrics component. Now they [default camel metrics](/components/next/micrometer-component.html#_default_camel_metrics) are provided by the Micrometer Component. As you can see in the documentations, there are some changes in the naming and the metrics.
+
+
+> **_NOTE:_** There has been some recent change in the Micrometer Camel component on naming conventions so depending on your camel version you can expect **'CamelExchangesTotal'** to change to **'camel.exchanges.total'** starting from Camel 4. Please refer to the [compatibility matrix](/camel-k/next/index.html#_compatibility_matrix) to know which version of Camel is used.
+
+One of the most important change concerns the notions of *route* and *context* in the metrics:
+```
+# Microprofile metrics
+# HELP application_camel_context_exchanges_total The total number of exchanges for a route or Camel Context
+# TYPE application_camel_context_exchanges_total counter
+application_camel_context_exchanges_total{camelContext="camel-1"} 0.0
+# HELP application_camel_route_exchanges_total The total number of exchanges for a route or Camel Context
+# TYPE application_camel_route_exchanges_total counter
+application_camel_route_exchanges_total{camelContext="camel-1",routeId="route1"} 0.0
+application_camel_route_exchanges_total{camelContext="camel-1",routeId="route2"} 0.0
+
+# Micrometer metrics
+# TYPE CamelExchangesTotal counter
+# HELP CamelExchangesTotal Total number of processed exchanges
+CamelExchangesTotal_total{camelContext="camel-1",routeId="route2",serviceName="MicrometerRoutePolicyService"} 0.0
+CamelExchangesTotal_total{camelContext="camel-1",routeId="route1",serviceName="MicrometerRoutePolicyService"} 0.0
+```
+
+The best way to anticipate the changes you should expect is to verify the exposed metrics accessing to _/q/metrics_ endpoint of your integrations as explained in the blog post about [monitoring](/blog/2022/07/camel-k-monitoring-ops/).
+
+
+# Conclusion
+
+As Metric is one of the pillar of Observability, this blog gave a better understanding on how to embrace the changes introduced in Camel K 2.0.
+
+If you have any feedback, ideas or find a new issue, please [create a new issue report in GitHub](https://github.com/apache/camel-k/issues)!
\ No newline at end of file
[camel-website] 02/02: chore: fix example link in camel-k prometheus blog post
Posted by pc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit dd7f976ce1552291cffb6644af41d38d8b400b10
Author: Gaelle Fournier <ga...@gmail.com>
AuthorDate: Thu Aug 3 11:00:06 2023 +0200
chore: fix example link in camel-k prometheus blog post
---
content/blog/2022/07/camel-k-monitoring-ops/index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/blog/2022/07/camel-k-monitoring-ops/index.md b/content/blog/2022/07/camel-k-monitoring-ops/index.md
index 509dd690..d493e6c0 100644
--- a/content/blog/2022/07/camel-k-monitoring-ops/index.md
+++ b/content/blog/2022/07/camel-k-monitoring-ops/index.md
@@ -38,10 +38,10 @@ Now, you can open your browser to http://localhost:9090, http://localhost:3000,
## Run a Camel K Integration with Prometheus trait
-We have prepared the field to play. Now we need to run some Camel K application in order to see it in action. We're using a simple REST API application to show how to monitor an Integration in Camel K. Let's use this [Camel K REST API example](https://github.com/apache/camel-k/blob/main/examples/rest/RestDSL.java). In order to perform all the configuration required to expose the metrics we can rely on [Prometheus trait](/camel-k/next/traits/prometheus.html). As we already have a Promethe [...]
+We have prepared the field to play. Now we need to run some Camel K application in order to see it in action. We're using a simple REST API application to show how to monitor an Integration in Camel K. Let's use this [Camel K REST API example](https://github.com/apache/camel-k-examples/blob/main/generic-examples/rest/RestDSL.java). In order to perform all the configuration required to expose the metrics we can rely on [Prometheus trait](/camel-k/next/traits/prometheus.html). As we alread [...]
```
-kamel run https://raw.githubusercontent.com/apache/camel-k/main/examples/rest/RestDSL.java --dev -t prometheus.enabled=true
+kamel run https://raw.githubusercontent.com/apache/camel-k-examples/main/generic-examples/rest/RestDSL.java --dev -t prometheus.enabled=true
```
## Check Microprofile metrics and Prometheus target