-
Issue #2064 cataloged all Java and Scala HTTP client and server frameworks that the agent instruments. All the Java based libraries were tested. This issue is for testing the Scala specific libraries.…
-
**What are you trying to achieve?**
I would like a convention on how the log bridges should report:
- logger name
- log bridge [package] name
- log bridge [package] version
Thanks to this bac…
-
### Is your feature request related to a problem? Please describe
The OTEL operator uses `auto-instrumentations-node`, however the dependency does not initialize metrics exporters (otlp and P…
-
-
> The current PR might be good enough as is for this topic. It might be worth creating a follow up issue for the work to ensure the used instrumentation version values are in sync with th…
-
**Background**
We are currently working on instrumenting the Cosmos DB SDK to capture CPU usage and related performance metrics in a way that is compatible with OpenTelemetry. Customers can leverage …
-
Just wondering if this container is intentionally broken? If I switch to `auto-instrumented` the demo app works.
**Versions**
- repo (git rev-list --max-count=1 HEAD): `c96df65755051bb5d5e…
-
All instrumentation libraries in contrib should be required to get a tracer manually with the schema_url they are using for the attributes used in the telemetry.
-
While I have added support for emitting function calls conforming to Go ABI (passing parameters on stack) for binary rewriting, it is not sufficient. The key issue is that if we call a function writte…
-
Hello OTel community. I've had one or two conversations with organizations interested in using a Perl implementation of OpenTelemetry. This issue is to gauge interest in maintaining a Perl implementat…