opentelemetry

Instruments .NET apps with OpenTelemetry to collect distributed traces and metrics.

4|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill opentelemetry-faysilalshareef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opentelemetry
Source: https://github.com/FaysilAlshareef/dotnet-ai-kit/tree/main/skills/observability/opentelemetry
Command: npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill opentelemetry-faysilalshareef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instrumentation for .NET applications to collect distributed traces and metrics, enabling end-to-end visibility across services and systems.

Core Features & Use Cases

  • Instrument .NET apps using a static ActivitySource and the OpenTelemetry SDK for consistent tracing across components.
  • Configure exporters (OTLP, console, and backend dashboards) to observe performance in development and production.
  • Define resource naming and instrumentation patterns to identify traces across web APIs, background services, and microservices.

Quick Start

Configure OpenTelemetry in your .NET project and verify that traces appear in your backend of choice.

Frequently Asked Questions about opentelemetry

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

FAQPage Schema
How do I instrument .NET apps for distributed tracing and metrics?

Instrument .NET apps by configuring a static ActivitySource and the OpenTelemetry SDK to collect distributed traces and metrics, ensuring end-to-end visibility across web APIs, background services, and microservices.

What backends can I export OpenTelemetry traces and metrics to?

Export OpenTelemetry traces and metrics to backends like Jaeger, Grafana Tempo, or Aspire Dashboard using configurable OTLP exporters, enabling performance observation across development and production environments.

Can I use OpenTelemetry to monitor ASP.NET Core web APIs and background services?

Yes, OpenTelemetry supports instrumenting ASP.NET Core web APIs, background services, and microservices, enforcing resource naming and consistent instrumentation patterns to identify traces across distributed environments.

What's the best way to configure OTLP exporters for .NET observability?

Configure OTLP exporters in your .NET project by defining resource naming and instrumentation patterns, allowing traces and metrics to be exported to backend dashboards for unified observability across environments.

Why do I need a static ActivitySource for .NET tracing?

A static ActivitySource provides consistent tracing across .NET application components, enabling the OpenTelemetry SDK to collect and export distributed traces and metrics efficiently to your chosen observability backend.

Does OpenTelemetry instrumentation work for microservices requiring unified observability?

Yes, OpenTelemetry instrumentation is designed for microservices requiring unified observability, supporting distributed traces and metrics across web APIs and background services with configurable exporters.