otel-observability-mindset

OpenTelemetry tracing for MediatR handlers in .NET requires using established decorator and tagging patterns to ensure consistent ActivitySource instrumentation. This skill guides developers to verify telemetry boundaries are correctly applied during handler development and code review.

Instrumenting external dependencies for observability in .NET involves wrapping clients for tracing and registering them in ServiceDefaults with appropriate health checks. This skill provides a checklist to ensure HTTP, SQL, and LLM integrations adhere to existing telemetry patterns.

Missing telemetry data in production often occurs when new code fails to integrate with existing OpenTelemetry infrastructure, creating fragmented observability gaps. This skill prevents these gaps by enforcing consistent ActivitySource, Meter, and Serilog logging patterns.

Yes, this observability skill is designed specifically for .NET 10.0 applications and requires adherence to established ActivitySource, Meter, and Serilog patterns defined in the repository's ServiceDefaults. It ensures consistent OpenTelemetry-driven operability across the application.

Extending existing ActivitySources and Meters without fragmentation requires following the repository's established ServiceDefaults patterns rather than creating new telemetry instances. This skill provides a mental model and checklist for standardized instrumentation across new code.

OpenTelemetry boundary enforcement for background services should be applied whenever developing or reviewing code that interacts with external dependencies or processes asynchronous tasks. This skill ensures background services maintain consistent tracing and logging standards.