[
https://issues.apache.org/jira/browse/CAMEL-23650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18086045#comment-18086045
]
Pasquale Congiusti commented on CAMEL-23650:
--------------------------------------------
PR in [https://github.com/apache/camel/pull/23751]
I analyzed it better and it does not make sense to introduce any further
configuration, but just lowering the log level. As for the usage during
development, it makes sense to disable, and the jbang is taking care to do it
now.
However, this was only enabled via `–observe` flag. During development this
flag should probably turned off. When enabled, it takes care to include the
observability services [1], which clarifies that, in case a user does not want
the feature, has to turn it off. This is what we're doing now by default in
Camel JBang.
[1]
[https://camel.apache.org/components/next/others/observability-services.html#_default_logging_metrics_on_shutdown]
> 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
> Assignee: Pasquale Congiusti
> Priority: Minor
> 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)
