Blog post featured image

We already explained how to take monitor your Integrations in the previous blog post about monitoring operations on Camel K. The good news is there are only a few changes with the move to Micrometer Metrics.

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 implementation.

The reason is the deprecation notice from Quarkus Microprile’s implementation in favor of using Micrometer Metrics. This decision follows a long period of transition 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 where provided by the camel Microprofile Metrics component. Now they 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.

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.

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!

Camel K Observability: Distributed Tracing

 , by

Tracing is an important approach for controlling and monitoring the experience of users, it allows us to gather more information about an integration’s performance. Camel K has been providing support for distributed tracing using OpenTracing since long time. At the beginning of 2022, the CNCF announced that they were archiving the OpenTracing project in favor of the OpenTelemetry project. OpenTelemetry is the latest solution created by merging OpenTracing and OpenCensus. As a result, we decided in Camel K 1.

Continue reading ❯

CAMEL KFEATURESDEVOPS

Camel K CICD

 , by

In Camel K version 10, we’ve released the CLI `promote feature that provides Camel K an opinionated way of promoting an Integration through the stages of software development. This feature unlock the possibility to combine Camel K with external tooling and let the user develop according to any automated release process. We always ear about CI/CD (Continuous Integration/Continuous Delivery and/or Deployment), and in this blog we’re going to see how to make it for any Camel K integration.

Continue reading ❯

HOWTOSCAMEL KDEVOPS

Camel K Operations: monitoring

 , by

Camel K offers a wide list of operations you can execute once your Integration has been deployed (likely in a production environment). When we talk about operations, the most typical question we got is “How to monitor a Camel K Integration?”. Fortunately, we have all the ingredients needed to let you manage this operation as smooth as possible. I’ll walk you through the different tools and configuration needed in this blog post.

Continue reading ❯

CAMEL KFEATURES

Camel K 1.5 - New configuration settings

 , by

Camel K version 1.5 is out. And with it, a new way of providing configuration and resources to your Integration. We have worked on a deep code refactoring in order to harmonize the existing configuration settings and add new ones to exploit the power of camel-quarkus runtime, which has become the main way to materialize an Integration. We added new features that will simplify your developer life. We also added new checks that will give you useful tips when using a feature in a wrong way.

Continue reading ❯

FEATURESCAMEL K