[jira] [Commented] (CAMEL-22704) camel-opentelemetry - Allow to capture existing camel component JMX metrics

[Pasquale Congiusti (Jira)]

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

Pasquale Congiusti commented on CAMEL-22704:
--------------------------------------------

We have an extension mechanism already in place that probably can work to 
collect any additional metrics required by each component. See the 
https://github.com/apache/camel/blob/main/components/camel-telemetry/src/main/java/org/apache/camel/telemetry/decorators/SedaSpanDecorator.java
 and, as a reference for implementation, 
https://github.com/apache/camel/blob/main/components/camel-telemetry/src/main/java/org/apache/camel/telemetry/decorators/KafkaSpanDecorator.java

> camel-opentelemetry - Allow to capture existing camel component JMX metrics
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-22704
>                 URL: https://issues.apache.org/jira/browse/CAMEL-22704
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-opentelemetry
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 4.x
>
>
> [#camel > OpenTelemetry component metrics @ 
> 💬|https://camel.zulipchat.com/#narrow/channel/257298-camel/topic/OpenTelemetry.20component.20metrics/near/557886146]
>  
> Maybe we can make it possible to configure otel to tell it to capture some 
> JMX attribute as custom metrics like queue depth on seda endpoints, or 
> something else.
>  



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