telemetry-dotnet-logging-plugin

What problem does it solve?

Jarvis's default OpenTelemetry logging configuration only supports built-in OTLP and console exporters, leaving no native way to route logs to custom or proprietary monitoring services without modifying core framework code.

Core Features & Use Cases

• Custom Exporter Registration: Implement and register the ILoggingExporter interface to add non-default log export targets to your Jarvis application.
• Seamless Framework Integration: Works with Jarvis's existing OpenTelemetry setup without overriding default logging behavior or requiring changes to core package code.
• Use Case: For example, if your organization uses an internal log aggregation platform that is not compatible with OTLP, you can use this Skill to implement a custom exporter that routes logs to that platform while retaining Jarvis's default console and OTLP logging.

Quick Start

Use the telemetry-dotnet-logging-plugin skill to register a custom ILoggingExporter that sends logs to your team's internal monitoring service alongside Jarvis's default OTLP and console exporters.