(camel) branch main updated: chore(components): log process and jvm metrics on shutdown

[pc...@apache.org]

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

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


The following commit(s) were added to refs/heads/main by this push:
     new 2551615e4e58 chore(components): log process and jvm metrics on shutdown
2551615e4e58 is described below

commit 2551615e4e58c82a13293e1ebb46ed4dc2489128
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Fri Apr 24 10:55:21 2026 +0200

    chore(components): log process and jvm metrics on shutdown
---
 .../src/main/docs/observability-services.adoc                           | 2 +-
 .../src/main/resources/observability-services.properties                | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/components/camel-observability-services/src/main/docs/observability-services.adoc b/components/camel-observability-services/src/main/docs/observability-services.adoc
index 76773714fc6a..1fdfa110ffcf 100644
--- a/components/camel-observability-services/src/main/docs/observability-services.adoc
+++ b/components/camel-observability-services/src/main/docs/observability-services.adoc
@@ -82,7 +82,7 @@ NOTE: feature available since version 4.19.0
 
 The presence of this component will make sure that when the application is shutting down, certain metrics are stored on log of the application in order to be preserved for any future analysis or shared with your log aggregator. This could be a solution to investigate how many exchanges were processed, how many have failed, etc, on an application that has a sudden or even a controlled shutdown. You can think on a cronjob running and being able at any moment to learn certain stats without  [...]
 
-You can even change `camel.metrics.logMetricsOnShutdown` and `camel.metrics.logMetricsOnShutdownFilters` in order to qualify better this behavior, which defaults to `true` and `app.info,camel.exchanges.*` by default.
+You can even change `camel.metrics.logMetricsOnShutdown` and `camel.metrics.logMetricsOnShutdownFilters` in order to qualify better this behavior, which defaults to `true` and exchanges, application and jvm memory metrics by default.
 
 === OpenTelemetry configuration
 
diff --git a/components/camel-observability-services/src/main/resources/observability-services.properties b/components/camel-observability-services/src/main/resources/observability-services.properties
index 61b55dcbe3d6..fc7a3a700c53 100644
--- a/components/camel-observability-services/src/main/resources/observability-services.properties
+++ b/components/camel-observability-services/src/main/resources/observability-services.properties
@@ -29,6 +29,6 @@ camel.metrics.path=/observe/metrics
 # used for regular container/JVM monitoring
 camel.metrics.binders=uptime,processor,jvm-info,jvm-memory,jvm-thread,jvm-gc
 camel.metrics.logMetricsOnShutdown=true
-camel.metrics.logMetricsOnShutdownFilters=app.info,camel.exchanges.*
+camel.metrics.logMetricsOnShutdownFilters=app.info,camel.exchanges.*,process.cpu.usage,jvm.memory.max,jvm.memory.used
 # Opentelemetry
 camel.opentelemetry2.enabled=true