telemetry-dotnet-metric-plugin

You can add custom application metrics to the .NET Jarvis OpenTelemetry pipeline by registering custom IMetricInstrumentation implementations into the MeterProviderBuilder using standard dependency injection.

Yes, you can track business-specific metrics like order processing latency in ASP.NET Core by extending the default Jarvis OpenTelemetry configuration with custom metric instrumentation, avoiding core framework code modifications.

Custom metric instrumentation extends the default OpenTelemetry setup by appending your application-specific meters to the existing prebuilt runtime and ASP.NET Core metrics through dependency injection registration.

The best way to export custom .NET metrics to additional targets is by adding custom IMetricExporter implementations to route your application-specific metrics beyond the default Jarvis OpenTelemetry configuration.

No, the telemetry-dotnet-metric-plugin does not require modifying existing dependencies, as it integrates custom IMetricInstrumentation and IMetricExporter implementations into the Jarvis pipeline via standard dependency injection.

You need custom metric instrumentation for your Jarvis .NET application when you must track operational or business metrics beyond the preconfigured runtime and ASP.NET Core metrics included by default.