logging-observability

Implement Serilog structured logging, correlation IDs, health checks, and OpenTelemetry in ASP.NET Core Razor Pages.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill logging-observability-agibuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging-observability
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/logging-observability
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill logging-observability-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive patterns for implementing robust logging, correlation IDs, health checks, and distributed tracing in ASP.NET Core applications, making it easier to monitor, debug, and troubleshoot production environments.

Core Features & Use Cases

  • Structured Logging: Integrates Serilog for JSON-formatted, searchable logs.
  • Correlation IDs: Ensures requests can be traced across distributed systems.
  • Health Checks: Configures endpoints to monitor application and dependency health.
  • OpenTelemetry: Facilitates integration with distributed tracing and metrics systems.
  • Use Case: When deploying a new ASP.NET Core microservice, use this Skill to ensure it emits structured logs with correlation IDs and exposes a health check endpoint, allowing seamless integration into your existing observability stack.

Quick Start

Configure Serilog for structured logging in your ASP.NET Core application by following the provided Program.cs and appsettings.json examples.

Frequently Asked Questions about logging-observability

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

FAQPage Schema
How do I set up structured logging with Serilog in ASP.NET Core Razor Pages?

Structured logging with Serilog in ASP.NET Core is configured by updating Program.cs and appsettings.json to emit JSON-formatted, searchable logs. This enables production-grade diagnostic monitoring for web applications.

How do I implement distributed tracing with OpenTelemetry in a .NET microservice?

Distributed tracing with OpenTelemetry in .NET is implemented by integrating the SDK into your ASP.NET Core application to export metrics and traces. This connects your microservices to external observability systems.

What's the best way to add correlation IDs to ASP.NET Core request logging?

Adding correlation IDs to ASP.NET Core request logging ensures individual requests can be traced across distributed systems. This is achieved by configuring structured logging patterns that tag every log entry with a unique identifier.

Does ASP.NET Core have built-in support for configuring health check endpoints?

ASP.NET Core supports configuring dedicated health check endpoints to monitor application and dependency health. This allows seamless integration into existing observability stacks to verify production uptime.

Can I use this observability setup for an existing ASP.NET Core web application?

You can apply these observability patterns to existing ASP.NET Core applications by updating your Program.cs configuration. It provides Serilog, correlation IDs, and health checks without requiring external dependencies.