How does this skill handle sensitive data?

It enforces strict security principles to never log secrets, JWTs, credentials, or user-specific content to maintain compliance and security.

Does it support request tracing?

Yes, the skill includes guidelines for attaching request_id fields to API handlers to ensure logs can be correlated across complex request flows.

When should I use Sentry according to this skill?

Use Sentry only for high-severity issues like infrastructure faults, auth failures, or database unavailability, while skipping it for routine validation or transient errors.

What logging library does this skill use?

This skill specifically promotes and implements patterns for the zerolog library in Go to provide high-performance, structured JSON logging.

Go Structured Logging

Name: Go Structured Logging
Author: Harvey-AU

byHarvey-AU

•

Analíticas y Monitorización

Implements standardized structured logging patterns using zerolog for Go applications to ensure consistent observability and error tracking.

Acerca de

This skill provides Claude with domain-specific guidance for implementing high-quality logging in Go projects using the zerolog library. It establishes clear protocols for log level selection, contextual field attachment, and error handling, while ensuring sensitive information like secrets or JWTs are never leaked. By following these patterns, developers can maintain a clean, searchable log stream that facilitates easier debugging and integrates seamlessly with monitoring tools like Sentry for critical infrastructure alerts, avoiding log bloat and double-logging.

Características Principales

Clear criteria for log level selection (Debug, Info, Warn, Error)
1 GitHub stars
Security-first logging to prevent sensitive data exposure
Best practices for error attachment and request correlation
Standardized zerolog implementation with contextual fields
Sentry integration guidelines for high-severity issues

Casos de Uso

Implementing request-ID correlation for tracing API handlers
Configuring automated error reporting for critical infrastructure failures
Standardizing logging across a Go-based microservices architecture

Acerca de

Características Principales

Clear criteria for log level selection (Debug, Info, Warn, Error)
1 GitHub stars
Security-first logging to prevent sensitive data exposure
Best practices for error attachment and request correlation
Standardized zerolog implementation with contextual fields
Sentry integration guidelines for high-severity issues

Casos de Uso

Implementing request-ID correlation for tracing API handlers
Configuring automated error reporting for critical infrastructure failures
Standardizing logging across a Go-based microservices architecture