telemetry-dotnet-logging-plugin

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.

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.

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.

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.

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.