Alan West

Often libraries are built on top of other libraries. We currently have a few examples that, when both libraries are instrumented, different design decisions have been made. ## Examples ###...

Adding gRPC instrumentation but not HttpClient causes issues with parenting

3

Both the gRPC .NET and HttpClient libraries generate their own Activity for outgoing calls. gRPC .NET uses HttpClient behind the scenes, so when you configure OpenTelemetry with both gRPC and...

Consider `http.status_code_class` attribute

10

Inspired by https://github.com/open-telemetry/opentelemetry-specification/pull/2943#issuecomment-1312400189. > because metrics are sensitive to cardinality, I've seen instrumentations using strings like 4xx, 5xx for status code. Proposal is to add a new attribute for grouping...

Adding gRPC instrumentation but not HttpClient causes issues with parenting

4

Both the gRPC .NET and HttpClient libraries generate their own Activity for outgoing calls. gRPC .NET uses HttpClient behind the scenes, so when you configure OpenTelemetry with both gRPC and...

Adding only HttpClient instrumentation to ASP.NET Core app does not work

10

# Bug Report If you only add HttpClient instrumentation to an ASP.NET Core app, no spans from HttpClient are collected. The issue is not specific to HttpClient instrumentation. I have...

[AspNetCoreInstrumentation] Incorrect value for `http.route` when using conventional routing

5

## Bug The `http.route` attribute is one of the more important HTTP attributes because users commonly wish to facet their metric and span data on `http.route` in order to understand...

[AspNetCoreInstrumentation] Incorrect value for `http.route` when using razor pages and invoking the root path

1

## Bug The `http.route` attribute is one of the more important HTTP attributes because users commonly wish to facet their metric and span data on `http.route` in order to understand...

Clarify and improve the OTLP exporter requirements of a retry strategy

5

The OTLP exporter specification lacks clarity with regards to its retry strategy. I have reviewed a number of implementations across languages as well as the collector. From what I have...

Review and audit of EventSource logging for self-diagnostics

1

OpenTelemetry .NET uses `EventSource` for internal logging. Each component defines an `EventSource` including the [API](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Api/Internal/OpenTelemetryApiEventSource.cs), [SDK](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry/Internal/OpenTelemetrySdkEventSource.cs), and each of the exporters and instrumentation components. The purpose of this issue is...