logging

Implement Serilog structured logging, OpenTelemetry tracing, metrics, and health checks for .NET applications.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/shahdanish/vibepos --skill logging-shahdanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging
Source: https://github.com/shahdanish/vibepos/tree/main/skills/logging
Command: npx skills add https://github.com/shahdanish/vibepos --skill logging-shahdanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logging and telemetry that are hard to search, correlate, and debug slow down incident response and make production issues difficult to diagnose.

Core Features & Use Cases

  • Structured logging with Serilog — emits queryable log events with named properties so you can filter and alert reliably.
  • OpenTelemetry tracing and metrics — connects requests across components and tracks performance and reliability over time.
  • Health checks for operational readiness — exposes clear liveness and readiness signals for orchestrators and load balancers.
  • Correlation IDs for end-to-end debugging — attaches a request identifier to all related logs and downstream calls to trace the full lifecycle.

Quick Start

Set up Serilog structured logging, add correlation ID middleware, and configure health endpoints so you can monitor application health and trace requests end-to-end.

Frequently Asked Questions about logging

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

FAQPage Schema
How do I implement structured logging with Serilog in a .NET application?

OpenTelemetry provides distributed tracing and metrics for .NET applications by connecting requests across components, tracking performance, and exporting telemetry data to monitor operational reliability.

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

Setting up health checks for .NET services involves exposing clear liveness and readiness signals through health endpoints, enabling orchestrators and load balancers to monitor operational readiness effectively.

What is the best way to trace requests end-to-end across .NET microservices?

Tracing requests end-to-end across .NET microservices is achieved by attaching a correlation ID to middleware, propagating the request identifier to all related logs and downstream calls for full lifecycle debugging.

Do I need OpenTelemetry to configure observability for my .NET web application?

Configuring observability for a .NET web application requires OpenTelemetry integration to export distributed traces and metrics, while Serilog handles structured event logging for reliable diagnostics.