logging

Configure Serilog and Sentry for structured logging with correlation IDs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/satish-krishna/sigil --skill logging-satish-krishna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging
Source: https://github.com/satish-krishna/sigil/tree/main/.claude/skills/logging
Command: npx skills add https://github.com/satish-krishna/sigil --skill logging-satish-krishna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralized, structured logging across backend and frontend using established patterns, with built-in safeguards to avoid exposing sensitive data and to enable cross-system tracing.

Core Features & Use Cases

  • Structured logging with Serilog on the backend for consistent JSON logs.
  • Sentry-based error tracking across server and client for unified alerts.
  • Correlation IDs and contextual enrichment to trace requests across services.

Quick Start

Configure Serilog on the backend, wire up Sentry on the frontend, and start emitting structured logs with correlation IDs to enable end-to-end observability.

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 across frontend and backend services?

Structured logging across frontend and backend is implemented using Serilog on the server for consistent JSON logs and Sentry on the client for unified error tracking, connected via correlation IDs for end-to-end observability.

What is the best way to trace requests across distributed services with correlation IDs?

Tracing requests across distributed services requires generating and propagating correlation IDs within your structured logs, enabling contextual enrichment to track a single request's path through both backend and frontend systems.

How do I configure Serilog for secure logging without exposing sensitive PII data?

Configuring Serilog for secure logging involves applying built-in safeguards and structured formats that consistently filter sensitive data, ensuring your backend JSON logs do not expose PII during cross-environment auditing.

Does Sentry work with Serilog for unified error tracking and observability?

Sentry works alongside Serilog by capturing frontend application errors while Serilog handles backend structured logs, together providing unified alerts and consistent cross-system tracing for debugging.

Can I use this structured logging setup for cross-environment configuration?

This structured logging setup supports cross-environment configuration, allowing you to maintain consistent log structures and secure contextual data handling across different deployment stages in your projects.