telemetry-dotnet-logging-plugin

12|2|Updated May 4, 2020

Search Tags:#csharp #logging #dotnet #opentelemetry #jarvis #custom-exporter

Ready to run

npx skills add https://github.com/hoangnh2412/jarvis --skill telemetry-dotnet-logging-plugin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: telemetry-dotnet-logging-plugin
Source: https://github.com/hoangnh2412/jarvis/tree/main/.opencode/skills/telemetry-dotnet/providers/logging-plugin
Command: npx skills add https://github.com/hoangnh2412/jarvis --skill telemetry-dotnet-logging-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about telemetry-dotnet-logging-plugin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add custom OpenTelemetry log exporters to a .NET backend?▼

Custom OpenTelemetry logging in .NET lets you route logs to proprietary monitoring services. You can implement the ILoggingExporter interface to add non-default export targets while retaining default console and OTLP logging.

Can I route .NET application logs to a non-OTLP monitoring service?▼

Yes, you can route .NET application logs to a non-OTLP monitoring service by registering a custom ILoggingExporter implementation. This extends logging capabilities beyond built-in OTLP and console exporters without altering core packages.

Does the Jarvis framework support custom log processing pipelines in .NET 9?▼

The Jarvis framework supports custom log processing pipelines in .NET 9 through its built-in ILoggingExporter dependency injection registration pattern, enabling integration of non-standard log export logic alongside default configurations.

How do I implement a custom ILoggingExporter for OpenTelemetry?▼

To implement a custom ILoggingExporter for OpenTelemetry, create a class implementing the interface and register it via dependency injection. This adds proprietary or third-party logging platform targets to your Jarvis application seamlessly.

What are the limitations of built-in OpenTelemetry exporters in Jarvis?▼

The limitation of built-in OpenTelemetry exporters in Jarvis is that they only support default OTLP and console outputs. Extending logs to custom aggregation platforms requires implementing the ILoggingExporter interface.