validate_telemetry

Local OpenTelemetry stack validation fails if the Aspire dashboard is unreachable or the OTEL_EXPORTER_OTLP_ENDPOINT is not set. Ensure both the dashboard and endpoint environment variable are properly configured before running validation.

Validate OpenTelemetry traces locally by automating the verification of emitted telemetry against a written narrative spec or passing a generic health check. This confirms instrumented services publish correct traces and metrics before deployment.

Telemetry validation against a narrative spec is the process of checking that locally emitted traces and metrics align with expected operational behaviors. It delegates to the observability-driven-development skill's Validation section to verify correctness.

You need the Aspire dashboard to be reachable and the OTEL_EXPORTER_OTLP_ENDPOINT environment variable set. An optional spec-file path can be provided to drive spec-based validation during the local health check.

Yes, you can run telemetry health checks in CI pipelines to verify instrumented services. The validation process applies to CI checks and operational health assessments where confirming telemetry correctness before deployment is required.

Local OpenTelemetry stack validation fails if the Aspire dashboard is unreachable or the OTEL_EXPORTER_OTLP_ENDPOINT is not set. Ensure both the dashboard and endpoint environment variable are properly configured before running validation.