Configuring OpenTelemetry .NET

by dotnet

Configuring OpenTelemetry .NET is a DevOps skill for Claude Code, published by dotnet in skills.

5.2K stars384 forkson dotnet/skillsAdded 2026/08/16Repository updated 2026/08/15

View source on GitHub Download repo ZIP

agent-skills

Install in seconds

Install Configuring OpenTelemetry .NET

Copy Configuring OpenTelemetry .NET into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/dotnet/skills/tree/main/plugins/dotnet-aspnetcore/skills/configuring-opentelemetry-dotnet ~/.claude/skills/configuring-opentelemetry-dotnet

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/dotnet/skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: plugins/dotnet-aspnetcore/skills/configuring-opentelemetry-dotnet/SKILL.md in dotnet/skills
Installs to: ~/.claude/skills/configuring-opentelemetry-dotnet
Collection: One of 25 skills cataloged from this repository
Category: DevOps — 798 skills

What Configuring OpenTelemetry .NET does

Configuring OpenTelemetry .NET sets up distributed tracing, metrics, and logging in ASP.NET Core using the .NET OpenTelemetry SDK. Use it when adding observability, configuring OTLP exporters, creating custom metrics or spans, or troubleshooting trace correlation.

Configuring OpenTelemetry .NET is cataloged under DevOps on DirSkills. Configuring OpenTelemetry .NET comes from a repository tagged agent-skills.

Documentation

README

Excerpt

Configuring OpenTelemetry in .NET

When to Use

Adding distributed tracing to an ASP.NET Core application
Setting up OpenTelemetry exporters (OTLP is the primary protocol; Jaeger accepts OTLP natively; Prometheus OTLP ingestion requires explicit opt-in)
Creating custom metrics or trace spans for business operations
Troubleshooting distributed trace context propagation across services

When Not to Use

The user wants application-level logging only (use ILogger, Serilog)
The user is using Application Insights SDK directly (different API)
The user needs APM with a commercial vendor's proprietary SDK

Inputs

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Configuring OpenTelemetry .NET

What else does dotnet publish alongside Configuring OpenTelemetry .NET?
Configuring OpenTelemetry .NET is one of 25 skills that DirSkills catalogs from dotnet/skills, the repository it ships in. Its siblings there include .NET P/Invoke, ASP.NET Core Web API and Agentic Workflows. Each one is a separate skill with its own page in this directory, installs the same way Configuring OpenTelemetry .NET does, and is maintained by dotnet in that same repository. The rest of the collection is listed on the dotnet/skills page.
How does Configuring OpenTelemetry .NET compare to other DevOps skills?
Configuring OpenTelemetry .NET ranks #151 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Configuring OpenTelemetry .NET against them. Open each page to compare what they document and how they install.