Does this skill work with all .NET versions?

It is designed for .NET applications that support the OpenTelemetry SDK, primarily targeting modern .NET (Core) versions 6.0 and later.

Can I use this for both traces and metrics?

Absolutely. It provides specific implementation patterns for both ActivitySources (for tracing) and Meters (for metrics).

How does it handle application performance?

The skill enforces a 'Resiliency First' approach and zero-allocation patterns, ensuring that telemetry collection logic never impacts main application processing.

Is it compatible with Prometheus and Jaeger?

Yes, by generating standard OTel-compliant data, your telemetry will be compatible with any observability backend that supports the OpenTelemetry protocol.

OpenTelemetry .NET Instrumentation

Name: OpenTelemetry .NET Instrumentation
Author: Aaronontheweb

byAaronontheweb

•

800

•

Analytics & Monitoring

Implements high-performance, standardized observability for .NET applications using OpenTelemetry best practices.

This skill provides comprehensive guidance and implementation patterns for adding distributed tracing and metrics to .NET codebases. It ensures that observability code follows OpenTelemetry semantic conventions and Microsoft's best practices while prioritizing application resiliency and performance. Whether you are instrumenting new microservices or auditing existing telemetry, this skill helps developers create robust, high-quality data for platforms like Jaeger, Prometheus, and Grafana by enforcing strict naming, error handling, and allocation-efficient patterns.

Key Features

01Strict adherence to OpenTelemetry semantic naming conventions for attributes

02Robust error handling and exception recording within spans

03Performance-optimized telemetry with zero-allocation fast paths

04Standardized ActivitySource and Meter configuration for .NET libraries

05800 GitHub stars

06Implementation of W3C-compliant distributed tracing and spans

Use Cases

01Auditing telemetry implementation for compliance with OTel semantic conventions

02Refactoring legacy diagnostic logging into standardized OpenTelemetry metrics

03Adding distributed tracing to a new .NET microservice or library

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add aaronontheweb/dotnet-skills opentelementry-dotnet-instrumentation

For use in Claude.ai and ChatGPT

Key Features

01Strict adherence to OpenTelemetry semantic naming conventions for attributes

02Robust error handling and exception recording within spans

03Performance-optimized telemetry with zero-allocation fast paths

04Standardized ActivitySource and Meter configuration for .NET libraries

05800 GitHub stars

06Implementation of W3C-compliant distributed tracing and spans

Use Cases

01Auditing telemetry implementation for compliance with OTel semantic conventions

02Refactoring legacy diagnostic logging into standardized OpenTelemetry metrics

03Adding distributed tracing to a new .NET microservice or library

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add aaronontheweb/dotnet-skills opentelementry-dotnet-instrumentation

For use in Claude.ai and ChatGPT