dotnet-structured-logging

Design log pipelines for .NET distributed systems with ELK, Seq, and Loki.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-structured-logging-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-structured-logging
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-structured-logging
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-structured-logging-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design, implement, and query robust log pipelines for .NET applications, ensuring efficient log management, analysis, and compliance in distributed systems.

Core Features & Use Cases

  • Log Aggregation Architecture: Explore options like ELK, Seq, and Grafana Loki, with recommended patterns using OTel Collector.
  • Structured Querying: Learn KQL, Seq Signal Expressions, and LogQL for effective log analysis across different platforms.
  • Log Sampling & PII Scrubbing: Implement strategies to manage log volume and protect sensitive data.
  • Cross-Service Correlation: Ensure you can trace requests across multiple services using Trace IDs and custom correlation.
  • Use Case: You need to set up a centralized logging system for your microservices. This Skill guides you through choosing an aggregation platform, configuring log shipping, and writing queries to troubleshoot a production issue that spans multiple services.

Quick Start

Configure an OpenTelemetry Collector to route .NET application logs to Elasticsearch and Loki.

Frequently Asked Questions about dotnet-structured-logging

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

FAQPage Schema
How do I set up structured logging in .NET distributed systems?

Structured logging in .NET involves configuring log pipelines with direct Serilog sinks or an OpenTelemetry Collector to route logs to aggregation platforms like ELK, Seq, or Grafana Loki for centralized analysis.

What is the best way to query logs across ELK, Seq, and Loki?

The best way to query logs across these platforms is using their specific structured query languages: KQL for ELK, Seq Signal Expressions for Seq, and LogQL for Grafana Loki to effectively analyze aggregated log data.

How do I trace requests across multiple microservices using .NET logs?

You trace requests across multiple .NET microservices by implementing cross-service correlation using Trace IDs and custom correlation identifiers within your structured logs to follow a request through various services.

How can I scrub PII and manage log volume in .NET applications?

You scrub PII and manage log volume in .NET applications by implementing log sampling strategies to reduce pipeline load and applying PII scrubbing techniques to ensure sensitive data is masked before log aggregation.

Does the OpenTe Collector work with Serilog for .NET log aggregation?

Yes, the OpenTelemetry Collector works with Serilog for .NET log aggregation by receiving emitted logs from Serilog sinks and routing them to backend platforms like Elasticsearch and Loki for centralized querying.