Claus Ibsen created CAMEL-23650:
-----------------------------------
Summary: camel-micrometer - Do not spam log at WARN in dev mode
Key: CAMEL-23650
URL: https://issues.apache.org/jira/browse/CAMEL-23650
Project: Camel
Issue Type: Improvement
Reporter: Claus Ibsen
Fix For: 4.21.0
2026-05-29 17:59:21.850 WARN 49747 --- [ main]
crometer.prometheus.MicrometerPrometheus : Micrometer service is stopping, here
a list of metrics collected so far.
2026-05-29 17:59:21.859 WARN 49747 --- [ main]
crometer.prometheus.MicrometerPrometheus : #METRIC-START## HELP app_info
#METRIC-END#
2026-05-29 17:59:21.859 WARN 49747 --- [ main]
crometer.prometheus.MicrometerPrometheus : #METRIC-START## TYPE app_info
gauge#METRIC-END#
2026-05-29 17:59:21.859 WARN 49747 --- [ main]
crometer.prometheus.MicrometerPrometheus :
#METRIC-START#app_info\{camel_context="timer-log",camel_runtime_provider="Main",camel_runtime_version="4.21.0-SNAPSHOT",camel_version="4.21.0-SNAPSHOT"}
1#METRIC-END#
2026-05-29 17:59:21.860 WARN 49747 --- [ main]
crometer.prometheus.MicrometerPrometheus : #METRIC-START## HELP
camel_exchanges_last_timestamp Last exchange processed time in milliseconds
since the Unix epoch#METRIC-END#
2026-05-29 17:59:21.860 WARN 49747 --- [ main]
crometer.prometheus.MicrometerPrometheus : #METRIC-START## TYPE
camel_exchanges_last_timestamp gauge#METRIC-END#
2026-05-29 17:59:21.860 WARN 49747 --- [ main]
crometer.prometheus.MicrometerPrometheus :
#METRIC-START#camel_exchanges_last_timestamp 1.780070361573E12#METRIC-END#
2026-05-29 17:59:21.860 WARN 49747 --- [ main]
crometer.prometheus.MicrometerPrometheus : #METRIC-START## HELP
jvm_memory_max_bytes The maximum amount of memory in bytes that can be used for
memory management#METRIC-END#
This seems to be for production use when a JVM is crashing and you hope to get
a little bit of logging before its dead.
But for developers that has fast feedback loop then this is annoying.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
