-
There's a few things that are missing and/or incoherent as documented here: https://github.com/open-telemetry/opentelemetry.io/issues/3247#issuecomment-1714034923
-
I've done a triage pass of failures seen in the OTBN regression when CDC instrumentation is enabled. To do this I compared the failures with the instrumentation on against the failures from the latest…
-
### Describe your environment
OS: Ubuntu
Python version: Python 3.9.19
Package version: 0.47b0
### What happened?
Attempt to build a Python project using opentelemetry.instrumentation.grpc usin…
-
The existing support for tracing via message attributes of an SQS message only appear to support the v1 API and it would be great to have v2 support, see https://github.com/openzipkin/zipkin-aws/tree/…
-
Current instrument is not support beego v2 on github.com/beego/beego
-
E.g. netty-3.8 instrumentation is tested with netty-4.0 and netty-4.1 instrumentations applied.
Should we apply this pattern to all instrumentations with multiple versions, or decide that the muzzl…
trask updated
2 years ago
-
Hi,
I'm trying to use the pika instrumentation and it looks like important basic attributes are missing.
I would like the next attributes to be instrumented:
- destination queue
- routing key
- e…
-
I've got an application instrumented with both hs-opentelemetry-instrumentation-wai and hs-opentelemetry-instrumentation-yesod. For the most part this works well, however I've found that the details …
-
### What version of OpenTelemetry are you using?
```
"@opentelemetry/auto-instrumentations-node": "^0.41.0",
"@opentelemetry/exporter-jaeger": "^1.21.0",
"@opentelemetry/exporter-t…
-
Other than e.g. the process instrumentation, the puma metrics do not include a hostname. In our setup, multiple puma containers report towards the same prometheus exporter. Without the hostname, they …
codez updated
2 years ago