dotnet-structured-logging

Design .NET log pipelines with ELK, Seq, and Loki aggregation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the complexity of managing and querying logs in distributed .NET applications, ensuring you can effectively aggregate, analyze, and secure your log data.

Core Features & Use Cases

  • Log Aggregation Architectures: Explore and implement ELK, Seq, Loki, and Azure Monitor pipelines.
  • Structured Querying: Learn platform-specific query languages (KQL, Seq Signals, LogQL) for efficient data retrieval.
  • PII Scrubbing & Correlation: Implement strategies to protect sensitive data and trace requests across services.
  • Use Case: Debug a critical production issue by quickly finding all log entries related to a specific TraceId across multiple microservices, even if they use different logging backends.

Quick Start

Use the dotnet-structured-logging skill to design a log aggregation pipeline using the OpenTelemetry Collector.

Frequently Asked Questions about dotnet-structured-logging

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

FAQPage Schema
How do I aggregate and query structured logs across distributed .NET microservices?

Cross-service correlation in .NET logging is achieved by tracing requests across services using a specific TraceId, allowing you to quickly find all related log entries across multiple microservices even when they use different logging backends.

What is the best way to configure the OpenTelemetry Collector for .NET log aggregation?

To scrub PII from .NET application logs, you implement specific strategies within your log pipeline design to protect sensitive data before it reaches the aggregation backend, ensuring compliance and security during post-emission log management.

Can I use Serilog with Seq and Loki for structured logging in .NET?

Structured querying in .NET log aggregation uses platform-specific query languages like KQL for Azure Monitor, Seq Signals, and LogQL for Loki, enabling efficient data retrieval and analysis from your aggregated log pipelines.

How do I implement PII scrubbing and cross-service correlation in .NET log pipelines?

Implementing PII scrubbing and cross-service correlation in .NET log pipelines requires designing strategies that protect sensitive data and trace requests across services, utilizing the OpenTelemetry Collector and Serilog for efficient data handling.