logging-observability

Standardize structured logging and integrate Sentry error tracking across backend services.

13|Updated Mar 15, 2019

Search Tags:#debugging #monitoring #logging #backend #observability #sentry #structured-logging

Ready to run

npx skills add https://github.com/WTFox/dotfiles --skill logging-observability-wtfox

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: logging-observability
Source: https://github.com/WTFox/dotfiles/tree/main/claude/.claude/skills/logging-observability
Command: npx skills add https://github.com/WTFox/dotfiles --skill logging-observability-wtfox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help teams design and enforce meaningful logging that supports debugging, monitoring, and safe data practices.

Core Features & Use Cases

Structured logging setup for production environments to enable fast querying and correlation.
Sentry integration for centralized error tracking and issue context.
Guidance on log levels, request tracing, and log content to avoid sensitive data exposure.

Quick Start

Integrate the provided logging configuration into your application and verify that structured logs and Sentry events are generated for a sample request.

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 for backend services to debug production issues?▼

Set up structured logging by standardizing log formats to enable fast querying and correlation across backend services. This approach enforces log level discipline and request ID tracing, turning production logs into actionable insights for efficient debugging.

What is the best way to integrate Sentry error tracking into my backend application?▼

Integrate Sentry error tracking by applying the provided configuration to your backend services to centralize error capture and issue context. This integration works alongside structured logging to monitor application health and debug production issues effectively.

How does request ID tracing work for correlating logs during debugging?▼

Request ID tracing works by assigning a unique identifier to each request and embedding it within structured logs. This enables fast querying and correlation across distributed backend services, allowing teams to trace execution paths and debug production issues efficiently.

How do I prevent sensitive data exposure when implementing application observability?▼

Prevent sensitive data exposure by applying safe logging practices and enforcing log content discipline within your observability strategy. This ensures structured logs and Sentry error tracking capture actionable debugging insights without exposing vulnerable information.

Can I use this structured logging configuration with existing backend monitoring tools?▼

Yes, the structured logging configuration integrates with existing backend monitoring workflows by standardizing log levels and formats. This compatibility ensures centralized error tracking via Sentry and fast log querying work seamlessly with your current observability tools.

What log levels should I use for monitoring production environments?▼

Use log level discipline to categorize severity when monitoring production environments, ensuring structured logs remain actionable and safe. This practice prevents log noise, enables fast querying, and supports accurate debugging alongside Sentry error tracking.