What problem does it solve?
MediatorLite users often struggle to get built-in logs and distributed traces working, cannot diagnose why observability emissions are missing, or need to eliminate logging and tracing overhead for performance-sensitive workloads like benchmarks without modifying library code.
Core Features & Use Cases
- Observability Configuration: Guides correct setup of MediatorLite's fixed Debug-level logging for the MediatorLite.IMediator category and OpenTelemetry tracing via the "MediatorLite" ActivitySource.
- Compile-Time Opt-Out: Explains how to use no-arg assembly attributes to completely strip logging and tracing emissions at compile time for zero-overhead scenarios.
- Troubleshooting: Helps diagnose common issues like missing logs due to incorrect filter levels, missing spans due to wrong ActivitySource names, or opt-out attributes applied in the wrong assembly.
- Use Case: A .NET developer adding OpenTelemetry to a MediatorLite-powered microservice can use this skill to correctly register the ActivitySource, adjust log filters, and verify spans are emitted without writing custom pipeline behaviors.
Quick Start
Use the mediatorlite-observability skill to configure OpenTelemetry tracing for your MediatorLite service and confirm that Send request spans appear in your exporter.