Скачать или смотреть .NET Aspire Doesn’t Play Nice with the OpenTelemetry Collector

Per the Practical OTEL developers, who are OpenTelemetry maintainers themselves:

-
It's considered best practice to use an OpenTelemetry Collector in production to perform telemetry sanitisation and curation using the Filter, Transform and Redaction processors amongst other uses. Since Aspire is replicating an environment like production, including telemetry, this provides a convenient way for you to test to ensure that your telemetry is able to be processed correctly.
-

This is a great idea and using the OpenTelemetry Collector locally also allows you to do things like keep your application-specific Grafana dashboards, Seq queries, et al in-play even as you debug locally using .NET Aspire.

However, despite following the best practices to configuring the OpenTelemetry Collector to work alongside .NET Aspire... It doesn't work! .NET Aspire 9.4 (and later, until they fix it) doesn't play nice with anyone else who needs to listen to the default `OTEL_EXPORTER_OTLP_ENDPOINT` value.

In this video we show you how to work around that issue in .NET Aspire and get the OTEL Collector and the Aspire dashboard working in-harmony together.

Materials used:

Practical OTEL Repo: https://github.com/practical-otel/ope...
Phobos Web Sample (Aspire + OTLP): https://github.com/petabridge/Petabri...
OpenTelemetry Collector: https://github.com/open-telemetry/ope...

Chapters:

00:00:00 Integrating .NET Aspire with OTEL Collector
00:00:31 Configuring OTEL_EXPORTER_OTLP_ENDPOINT in .NET Aspire
00:01:37 .NET Aspire Front-Runs OTEL_EXPORTER_OTLP_ENDPOINT
00:02:11 The Fix
00:02:29 Exporting Metrics to Prometheus, Grafana, Aspire, and Seq
00:02:51 Conclusion