You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "lsergio (via GitHub)" <gi...@apache.org> on 2024/12/17 16:57:20 UTC

[I] Telemetry addon configuration not working [camel-k]

lsergio opened a new issue, #6002:
URL: https://github.com/apache/camel-k/issues/6002

   ### What happened?
   
   Create the following Integration with telemetry configuration:
   
   ```apiVersion: camel.apache.org/v1
   kind: Integration
   metadata:
     name: bugtelemetry
   spec:  
     sources:
     - name: main.yaml
       content: |-
         - from:
             uri: rest:get:/demo
             steps:
             - setBody:
                 constant: "It worked"
     traits:
       health:
         enabled: true
       camel:
         runtimeVersion: 3.2.3
       addons:
         telemetry:
           auto: false
           enabled: true
           endpoint: http://simplest-collector-headless.jaeger.svc.cluster.local:4317
           sampler-ratio: "1.0"
           serviceName: Demo
   ```
   
   After it's running, submit some requests to the endpoint and monitor the log:
   Eventually we will ser an error exporting the spans:
   
   ```
   [1] 2024-12-17 16:52:06,352 SEVERE [io.ope.exp.int.grp.OkHttpGrpcExporter] (OkHttp http://localhost:4317/...) Failed to export spans. The request could not be executed. Full error message: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:4317
   ```
   
   Per the error message, the trait is trying to send tracing data to localhost and not the configured endpoint.
   
   
   
   
   ### Steps to reproduce
   
   _No response_
   
   ### Relevant log output
   
   _No response_
   
   ### Camel K version
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Telemetry addon configuration not working [camel-k]

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #6002:
URL: https://github.com/apache/camel-k/issues/6002#issuecomment-2555341628

   Hello. Thanks for reporting. Yeah, the problem with those properties is that unfortunately we see many changes. I think that, looking at the future of the product, we need to make things more flexible. We're deprecating those traits that are purely based on Camel properties, so, I think also the telemetry trait may go in that direction. At the end of the day, having to set a camel property or a Camel K trait, won't change that much from UX perspective.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Telemetry addon configuration not working [camel-k]

Posted by "lsergio (via GitHub)" <gi...@apache.org>.
lsergio commented on issue #6002:
URL: https://github.com/apache/camel-k/issues/6002#issuecomment-2549200913

   @squakez Per [Quarkus documentation](https://quarkus.io/guides/opentelemetry#quarkus-opentelemetry_quarkus-otel-exporter-otlp-traces-endpoint), the property is `quarkus.otel.exporter.otlp.traces.endpoint`, but [here](https://github.com/apache/camel-k/blob/release-2.4.x/pkg/resources/resources/camel-catalog-3.8.1.yaml#L147) I can see we're using `tracer`, not `traces`.
   
   My guess is that we have upgraded Quarkus and didn't realize the properties have changed.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Telemetry addon configuration not working [camel-k]

Posted by "lsergio (via GitHub)" <gi...@apache.org>.
lsergio commented on issue #6002:
URL: https://github.com/apache/camel-k/issues/6002#issuecomment-2549048476

   With runtime 3.15.0, the behavior is the same, although the error message changes a little bit:
   ```
   [1] 2024-12-17 17:01:05,486 WARNING [io.ope.exp.int.grp.GrpcExporter] (vert.x-eventloop-thread-1) Failed to export spans. Server responded with gRPC status code 2. Error message: Failed to export TraceRequestMarshalers. The request could not be executed. Full error message: Connection refused: localhost/127.0.0.1:4317
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Telemetry addon configuration not working [camel-k]

Posted by "lsergio (via GitHub)" <gi...@apache.org>.
lsergio commented on issue #6002:
URL: https://github.com/apache/camel-k/issues/6002#issuecomment-2556877072

    I see your point. At the end we might only need the trait or some sort of configuration to enable telemetry and include the required dependencies. Perhaps using the dependencies field on the spec is enough.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Telemetry addon configuration not working [camel-k]

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #6002: Telemetry addon configuration not working
URL: https://github.com/apache/camel-k/issues/6002


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Telemetry addon configuration not working [camel-k]

Posted by "lsergio (via GitHub)" <gi...@apache.org>.
lsergio commented on issue #6002:
URL: https://github.com/apache/camel-k/issues/6002#issuecomment-2549114738

   Adding properties to the camel trait fixes the issue:
   
   ```
       camel:
         runtimeVersion: 3.2.3
         properties:
         - quarkus.otel.exporter.otlp.traces.endpoint=http://simplest-collector-headless.jaeger.svc.cluster.local:4317
   ```
   
   It looks like the quarkus property names are not the expected ones when we use only the add on trait.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Telemetry addon configuration not working [camel-k]

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #6002:
URL: https://github.com/apache/camel-k/issues/6002#issuecomment-2549142368

   It's weird as we have E2E test for this. @gansheer any idea why we're not detecting this?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Telemetry addon configuration not working [camel-k]

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #6002:
URL: https://github.com/apache/camel-k/issues/6002#issuecomment-2558409858

   This one is intersecting with https://github.com/apache/camel-k/issues/5904 - ideally, when we provide some Camel property, we should be able to include the required dependency. In this way we enhance the UX as we limit the input required by the user to any given Camel property only.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Telemetry addon configuration not working [camel-k]

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #6002: Telemetry addon configuration not working
URL: https://github.com/apache/camel-k/issues/6002


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org