ce-logging-observability

Enforce structured logging and observability governance for calibrated_explanations modules.

78|15|Updated May 1, 2023
One-click install
npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-logging-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-logging-observability
Source: https://github.com/Moffran/calibrated_explanations/tree/main/.claude/skills/ce-logging-observability
Command: npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-logging-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to managing logging and observability across calibrated_explanations, ensuring compliance with ADR-028 and Standard-005 to reduce noise and improve auditability.

Core Features & Use Cases

  • Enforces consistent logger domains under the calibrated_explanations root: core, plugins, telemetry, governance.
  • Defines governance vs operational separation guidelines, including where to place audit events and performance metrics.
  • Provides guidance on structured logging, context propagation, and testing practices to support maintainability and safety.

Quick Start

Follow ADR-028 and Standard-005 to implement and validate standardized logging in your module.

Frequently Asked Questions about ce-logging-observability

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

FAQPage Schema
How do I implement structured logging and observability governance for Python libraries?

Structured logging governance is implemented by enforcing consistent logger domains, contextual tracing, and domain-based policies. This approach reduces log noise and improves auditability by separating governance events from operational metrics.

What are the standard logger domains for managing audit events and telemetry?

Standard logger domains are organized under a root namespace into core, plugins, telemetry, and governance. This categorization defines clear placement rules for audit events and performance metrics to maintain separation of concerns.

How do I separate governance logging from operational metrics during development workflows?

Governance logging separation is achieved by following specific guidelines that isolate audit events from performance metrics. Placing audit trails in the governance domain and runtime data in telemetry ensures maintainability and safety.

Does context propagation in structured logging require specific testing practices?

Context propagation requires dedicated testing practices to support maintainability and safety. Testing validates that contextual tracing correctly flows through development workflows and audit activities without losing state.

What is the best way to enforce ADR-028 and Standard-005 compliance for new module logging?

ADR-028 and Standard-005 compliance is enforced by applying standardized logging rules during new module development. Using provided context helpers mandates domain-based logging policies and ensures contextual tracing validation.