Alan West

[Bug]: OTLP exporter fails to send data to backend requiring TLS

4

### What happened? The following code worked with opentelemetry/opentelemetry_sdk 0.23.0 and opentelemetry-otlp 0.16.0 I have the following environment variables set * `OTEL_EXPORTER_OTLP_ENDPOINT=https://my-backend` * `OTEL_EXPORTER_OTLP_HEADERS=key-required-by-my-backend=value` #### Cargo.toml ```toml [package] name =...

Update SqlClient instrumentation to follow new DB span conventions

1

Fixes #2225 This PR is the first in a series of PRs. It introduces support for the `OTEL_SEMCONV_STABILITY_OPT_IN` environment variable to gate using the old or new conventions. It does...

### Component OpenTelemetry.Instrumentation.SqlClient ### What is the expected behavior? Adopt the new [span conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md) and gate them by the by the [`OTEL_SEMCONV_STABILITY_OPT_IN`](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/non-normative/db-migration.md) environment variable.

[sql] Parse `db.operation.name` and `db.collection.name` from `db.query.text`

1

### Component OpenTelemetry.Instrumentation.SqlClient ### What is the expected behavior? The attributes `db.operation.name` and `db.collection.name` are conditionally required "if readily available". Alternatively, they MAY be parsed from `db.query.text`. See [relevant footnotes](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md#common-attributes)....

### Component OpenTelemetry.Instrumentation.SqlClient ### What is the expected behavior? The collection of `db.query.text` is opt-in because it runs the risk of collecting sensitive information. Collecting `db.query.text` is often very valuable...

Entity Framework is an ORM. As such, the instrumentation for it supports many database systems. The semantic conventions differ from system to system. We must determine what unique requirements may...

### Component OpenTelemetry.Instrumentation.SqlClient ### What is the expected behavior? The [database span conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md#common-attributes) lists a number of attributes that should be provided at span creation time. > The following attributes...

OTLP exporters: Support instantiating one channel/connection for sending traces, metrics, and logs

4

Mentioned in this [comment](https://github.com/open-telemetry/opentelemetry-dotnet/pull/1964#issuecomment-929767871). Probably most applicable to OTLP/gRPC but may also be relevant to think about for OTLP/HTTP. Currently, instantiating an OTLP/gRPC exporter for traces, metrics and logs will...

Support for other implementations of .NET (Xamarin, Mono, etc)

1

Prior issues have been opened inquiring about [Xamarin](https://github.com/open-telemetry/opentelemetry-dotnet/issues/3101) and [Mono](https://github.com/open-telemetry/opentelemetry-dotnet/issues/2713) support. However, OpenTelemetry .NET has only ever been officially tested on .NET implementations including .NET (formerly .NET Core) and .NET...

No spans are emitted

2

I am trying to use actix-web-opentelemetry with the latest version of opentelemetry-rust. I am sending data to a local OpenTelemetry collector. I've modified the client/server example from this repository very...