telemetry-dotnet-trace-plugin

What problem does it solve?

Jarvis's core OpenTelemetry integration does not include built-in instrumentation for custom application-specific traces, leaving observability gaps for proprietary domain logic and unique operational workflows.

Core Features & Use Cases

• Custom Trace Source Registration: Implement the ITraceInstrumentation interface to add dedicated trace sources for your application's unique modules and operations.
• Supplementary Exporter Support: Register custom ITraceExporter implementations to send trace data to additional endpoints beyond the core OpenTelemetry exporters included in Jarvis.
• Use Case: For example, if you have built a custom order processing module in your Jarvis backend, you can use this skill to add trace sources for that module to monitor request latency, error rates, and end-to-end flow of order-related operations.

Quick Start

Use the telemetry-dotnet-trace-plugin skill to register custom trace sources for your order processing module in your Jarvis OpenTelemetry configuration.