logging-review

Assess Python logging configuration and trace correlation for production safety.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/jamesogunsan/prod-eng-skills --skill logging-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logging-review
Source: https://github.com/jamesogunsan/prod-eng-skills/tree/main/plugins/logging/skills/logging-review
Command: npx skills add https://github.com/jamesogunsan/prod-eng-skills --skill logging-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineering teams ensure their Python logging configuration is consistent, actionable, and production-safe, enabling reliable triage, better trace correlation, and safer rollout of changes.

Core Features & Use Cases

  • Centralized root logger discipline and use of named loggers to avoid silent logging.
  • Structured fields and context propagation to improve diagnosability across services.
  • Safe exception capture and preservation of valuable context.
  • Guardrails to prevent leakage of secrets, tokens, or excessive log volume.
  • Practical guidance for rollout, testing, and validation of logging changes.

Quick Start

Run a quick audit of the current Python logging configuration and propose immediate improvements.

Frequently Asked Questions about logging-review

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

FAQPage Schema
How do I audit Python logging configuration for noisy or missing logs in production?

Python logging audits enforce root and named logger discipline to eliminate silent logging gaps. This assesses structured context propagation and safe exception handling, ensuring production logs are consistent, actionable, and safe for reliable triage.

What is structured logging and how does it improve trace correlation across services?

Structured logging uses standardized fields and context propagation to improve diagnosability across services. Enforcing structured context ensures trace correlation can be accurately verified across distributed boundaries during production diagnostics.

How do I prevent secrets or tokens from leaking into application logs?

Preventing secrets from leaking into application logs requires applying guardrails that restrict sensitive data capture. This skill enforces safe exception handling and configuration guardrails to stop leakage of tokens or sensitive information.

What is the best way to verify trace propagation across boundaries in Python services?

Verifying trace propagation across boundaries requires assessing structured context fields and named logger outputs. This skill checks trace correlation across distributed service boundaries to ensure no diagnostic context is lost.

How do I safely roll out configuration changes to production logging without breaking diagnostics?

Safely rolling out production logging changes requires practical guidance for testing and validation. This skill enforces rollout-safe configuration changes to verify root logger discipline and structured fields without disrupting operability.

Why does my root logger silently drop logs in a Python service?

A root logger silently drops logs when named loggers lack proper configuration and structured context. Enforcing centralized root logger discipline and structured fields resolves silent logging issues and restores actionable production diagnostics.