Configure Serilog structured logging and health endpoints for .NET 10 services.
npx skills add https://github.com/Maj3D10/Training-Platform --skill logging-maj3d10
Please help me install this Agent Skill. Skill: logging Source: https://github.com/Maj3D10/Training-Platform/tree/main/.agent/skills/logging Command: npx skills add https://github.com/Maj3D10/Training-Platform --skill logging-maj3d10
This Skill solves the challenge of turning scattered application logs into reliable observability by providing structured logging, distributed tracing, and operational health signals that work together.
Use the logging skill to configure Serilog structured logs, correlation ID propagation, and /health/live and /health/ready endpoints for your .NET 10 application.
High-intent search queries and answers about installing and using this skill.
Configure Serilog structured logging in .NET by using LogContext enrichment to inject correlation IDs into message templates. This enables request-level diagnostics and allows you to track a single request across distributed logs and downstream calls.
You need separate liveness and readiness health check endpoints to validate runtime readiness in production. Routing /health/live and /health/ready separately distinguishes basic application availability from dependency readiness, preventing unnecessary pod restarts.
OpenTelemetry distributed tracing integrates with Serilog by aligning trace contexts with log correlation IDs. This ensures that metrics, traces, and structured log events share consistent correlation headers for seamless observability across downstream calls.
Yes, this structured logging setup is specifically designed for .NET 10 services. It standardizes application logging, applies Serilog structured message templates, and ensures production readiness checks are configured correctly.
The best way to follow a single request across application logs is by propagating correlation headers. Standardizing structured logs with a correlation ID ensures every log event across downstream calls shares the same traceable identifier.
Serilog structured logs lack request context when LogContext enrichment is not configured. Enriching message templates with machine name, application name, and correlation IDs turns scattered logs into searchable, filterable observability data.
mitkoxConfigure OpenTelemetry, Serilog, and Prometheus/Jaeger exporters for ASP.NET Core observability.
thc1006Implement full-stack observability for service mesh deployments with metrics, traces, and logs.
TrossitecConfigure Serilog structured logging in ASP.NET Core with sinks and enrichment.
mcj-coderConfigure Serilog with ILogger abstractions for standardized .NET application logging.
