skill-observability-logging

Standardize structured logs across Node.js and Python with Pino and Loguru.

4|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill skill-observability-logging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-observability-logging
Source: https://github.com/ryan-nguyen-01/agent-platform/tree/main/.claude/skills/skill-observability-logging
Command: npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill skill-observability-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent logging formats across Node.js and Python applications hinder debugging and log analysis. This Skill standardizes structured logging to improve traceability, security, and operational insights.

Core Features & Use Cases

  • Unified log formats for Node.js (Pino) and Python (Loguru).
  • Support for redaction of sensitive fields (e.g., passwords, tokens, secrets).
  • Request-id propagation and cross-service correlation.
  • Configurable outputs: pretty logs for development and JSON for production, with optional colorization.
  • Best practices for integration in microservices, web apps, and batch jobs.

Quick Start

Initialize the logger in your application by importing the library, setting environment-based output (pretty in development, JSON in production), and ensure redaction of sensitive fields.

Frequently Asked Questions about skill-observability-logging

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

FAQPage Schema
How do I standardize structured logging across Node.js and Python microservices?

Standardize structured logging by using Pino for Node.js and Loguru for Python to emit unified, language-agnostic JSON logs, ensuring consistent traceability and operational insights across microservices.

What is request-id propagation and how does it improve observability?

Request-id propagation is the mechanism of passing a unique identifier across services to correlate logs. It improves observability by enabling cross-service tracing for consistent debugging in distributed applications.

Does this logging approach support redaction of sensitive fields like passwords and tokens?

Yes, this logging approach supports redaction rules to automatically filter sensitive fields like passwords, tokens, and secrets from structured logs, enhancing security before centralized log aggregation.

Can I use pretty logs for development and JSON for production with Pino and Loguru?

Yes, you can configure environment-based outputs to use human-readable pretty logs with colorization during development and structured JSON formats for production using Pino and Loguru.

What is the best way to integrate structured logging into batch jobs?

The best way to integrate structured logging into batch jobs is to initialize environment-based outputs and apply redaction rules using Loguru or Pino, ensuring consistent tracing and centralized log aggregation.