-
With https://github.com/open-telemetry/semantic-conventions/pull/473 the `event.domain` and `event.name` are merged into a single field, where `event.domain` becomes a prefix.
So new event names fo…
-
-
`@opentelemetry/instrumentation-http` added the possibility to opt-in to the stable HTTP semantic conventions for span attributes
ref: https://github.com/open-telemetry/opentelemetry-js/pull/4978
As …
-
- **Package Name**: azure-monitor-opentelemetry-exporter
- **Package Version**: latest
- **Operating System**: n/a/
- **Python Version**: n/a
**Describe the bug**
The azure monitor opentelem…
-
I have a set of spans that I can use to monitor my HTTP services in DataDog, and I make use of a OTLP pipeline
```rust
opentelemetry_otlp::new_pipeline()
.tracing()
.with_exporter(
…
-
Not able to filter metrics with high cardanility such as net_sock_addr/port.
```
import (
"context"
"time"
"github.com/density-exchange/density-api/pkg/log"
"go.opentelemetry.io/otel"
…
-
### Is your instrumentation request related to a problem? Please describe
It's very useful to have metrics about platform runtime - heap status, GC metrics, event loop blocks etc...
OpenTelemetry …
-
### Description
Two of the metrics provided by the `otelhttp` package don't follow the semantic conventions. These metrics:
- `http.server.response_content_length` which should be called `http.ser…
-
`*.system` is a compile-time constant which is repetitive on spans and is a good candidate for instrumentation scope attribute.
AFAIK, not every OTel api impl supports them (https://github.com/dotn…
-
I have been fiddling with the playground sample for the playground OpenAI component trying to get it to emit telemetry. I think the following things are missing;
- Updating Directory.Packages.props…