dotnet:observability

Integrate structured logging, OpenTelemetry, and health checks into .NET applications.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-observability-dimsour
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet:observability
Source: https://github.com/dimsour/dotnet-ai-toolkit/tree/main/plugins/dotnet/skills/observability
Command: npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-observability-dimsour

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit offers comprehensive observability features for .NET applications, addressing the challenge of effective logging, monitoring, and tracing.

Core Features & Use Cases

  • Logging: Implement structured logging with ILogger<T>, avoiding console logging for production applications.
  • Structured Logging: Leverage LoggerMessage source generators for high-performance, allocation-free logging.
  • Scopes: Enable request correlation with the use of scopes to maintain context across asynchronous operations.
  • OpenTelemetry: Integrate OpenTelemetry for traces, metrics, and logs to gain insights into application performance.
  • Health Checks: Implement health checks to ensure application readiness and liveness.
  • Use Case: For a web application, this Skill unit can be used to set up structured logging and OpenTelemetry integration, ensuring detailed traces and metrics for monitoring and debugging.

Quick Start

Add observability to your .NET application by installing the dotnet:observability skill.

Frequently Asked Questions about dotnet:observability

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

FAQPage Schema
How do I add OpenTelemetry traces and metrics to a .NET application?

You can add OpenTelemetry traces and metrics to a .NET application by integrating the OpenTelemetry framework, which provides detailed insights into application performance and debugging.

What's the best way to implement structured logging in .NET to avoid console overhead?

The best way to implement structured logging in .NET is using `ILogger<T>` with LoggerMessage source generators, providing high-performance, allocation-free logging for production applications.

How do I maintain logging context across asynchronous operations in .NET?

You maintain logging context across asynchronous operations in .NET by using logging scopes, which enable request correlation to preserve context throughout the workflow.

Does this observability solution support .NET 8 applications?

Yes, this observability solution supports .NET 8 through .NET 11 applications, offering structured logging, OpenTelemetry integration, and health checks.

How do I set up health checks for application readiness and liveness in .NET?

You set up health checks for application readiness and liveness in .NET by implementing built-in health check features, ensuring your application reports its operational status accurately.

Why should I use LoggerMessage source generators instead of standard logging?

You should use LoggerMessage source generators instead of standard logging to achieve high-performance, allocation-free structured logging that avoids the overhead of traditional console logging.