telemetry-dotnet-trace-plugin

Custom trace sources are registered by implementing the ITraceInstrumentation interface to extend the TracerProviderBuilder. This allows you to monitor proprietary domain logic and unique operational workflows in your .NET backend without modifying core framework code.

You need custom trace instrumentation when built-in OpenTelemetry modules do not cover your proprietary domain logic. If you need to monitor request latency, error rates, or end-to-end flow for unique modules like order processing, custom trace sources fill those observability gaps.

Yes, you can add supplementary trace exporters to an existing OpenTelemetry pipeline by registering custom ITraceExporter implementations. This sends trace data to additional endpoints beyond the core OpenTelemetry exporters already included in your backend.

Yes, the telemetry-dotnet-trace-plugin applies directly to Jarvis backend applications. It extends the core Jarvis.OpenTelemetry integration to provide trace instrumentation for custom domain logic not covered by default modules.

The ITraceInstrumentation approach is limited to extending the TracerProviderBuilder for custom trace sources and supplementary exporters. It requires existing Jarvis.OpenTelemetry integration and does not automatically instrument proprietary logic without manual interface implementation.