Re: [I] [imporve] OpenTelemetry supports end-to-end testing [pulsar]

["lhotari (via GitHub)" <gi...@apache.org>]

lhotari commented on issue #24545:
URL: https://github.com/apache/pulsar/issues/24545#issuecomment-3106117690

   > In OpenTelemetry's OTLP mode, only a Go implementation of the Server is available. Consequently, when conducting end-to-end testing of the Pulsar OpenTelemetry client to the Server, we can only simulate the environment by launching Pods within the integration test module. However, it is impossible to retrieve actual data from the Server side, rendering the testing ineffective.
   
   @315157973 Just wondering if solving this problem belongs to the apache/pulsar code base. I noticed that OpenTelemetry provides and example in https://github.com/open-telemetry/opentelemetry-java-examples/tree/main/telemetry-testing, but that's not a very convenient solution either.
   
   For in-memory tests executed with Junit, there's already a solution for asserting Otel metrics. Why would apache/pulsar code base need to verify that the Otel Exporter traces get exported correctly?
   
   btw. In the OpenTelemetry code base, there seem to be somewhat a similar solution that you have added in the PR: https://github.com/open-telemetry/opentelemetry-java-contrib/blob/1f5f0d25ec4fdd907904135a9eb651fb0dd5c887/jmx-metrics/src/integrationTest/java/io/opentelemetry/contrib/jmxmetrics/AbstractIntegrationTest.java#L289-L320 . I was checking how they have solved a similar problem.
   


-- 
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@pulsar.apache.org

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