[ 
https://issues.apache.org/jira/browse/CAMEL-22695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050457#comment-18050457
 ] 

Cameron Fitzwater edited comment on CAMEL-22695 at 1/7/26 7:31 PM:
-------------------------------------------------------------------

[~davsclaus]  – did you have a chance to review my last comment?

When adding the contents of the observability-services.properties file to 
application.properties and trying to run with quarkus (via run or export), 
there are still issues / does not run clean and {*}/observe/metrics is not 
available{*}.

WORKS:
camel run * --runtime=camel-main --camel-version=4.14.0 
--dep=camel-opentelemetry2

DOES NOT WORK:
camel run * --runtime=quarkus --camel-version=4.14.0 --dep=camel-opentelemetry2


was (Author: JIRAUSER310023):
[~davsclaus]  – did you have a chance to review my last comment?

When adding the contents of the observability-services.properties file to 
application.properties and trying to run with quarkus (via run or export), 
there are still errors / does not run clean.

> camel-jbang: --observe flag being ignored
> -----------------------------------------
>
>                 Key: CAMEL-22695
>                 URL: https://issues.apache.org/jira/browse/CAMEL-22695
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jbang
>    Affects Versions: 4.x
>            Reporter: Cameron Fitzwater
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.14.3, 4.17.0
>
>
> When running a {{camel run}} or {{{}camel export{}}}, if you have an 
> application.properties file, it is no longer auto-enabling metrics when 
> having the {{--observe}} flag (it is completely ignored).
> We use this {{--observe}} flag in our pipeline, and even with jbang and camel 
> pinned to version, the same behavior is happening.
> This behavior changed recently, and I believe impacted all 4.X, per some 
> local testing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to