# Observability Logging

> Observability logging workflow for structured schema, correlation, and incident triage utility. Use when services need logging standards or revisions for diagnosable incidents; do not use for business-feature implementation logic.

- Skill: `planifest/observability-logging` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add planifest/observability-logging`
- Raw SKILL.md: https://api.skillmd.com/api/skills/planifest/observability-logging/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: planifest (https://skillmd.com/u/planifest)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/planifest/observability-logging

---


# Observability Logging

## Overview
Use this skill to standardize logs so incidents can be diagnosed quickly and safely.

## Scope Boundaries
- Use this skill when the task matches the trigger condition described in `description`.
- Do not use this skill when the primary task falls outside this skill's domain.

## Shared References
- Logging field and retention rules:
  - `references/logging-field-and-retention-rules.md`

## Templates And Assets
- Logging schema template:
  - `assets/logging-schema-template.md`
- Log triage checklist:
  - `assets/log-triage-checklist.md`

## Inputs To Gather
- Incident triage requirements and common failure modes.
- Required correlation fields and security constraints.
- Retention, redaction, and access policy requirements.
- Queryability needs for on-call workflows.

## Deliverables
- Logging schema and policy baseline.
- Redaction/retention controls.
- Triage validation evidence for key incident scenarios.

## Workflow
1. Define schema in `assets/logging-schema-template.md`.
2. Apply retention/redaction policy from `references/logging-field-and-retention-rules.md`.
3. Validate triage utility using `assets/log-triage-checklist.md`.
4. Fix gaps in correlation and error context fields.
5. Publish logging standard and ownership.

## Quality Standard
- Logs contain required triage context and correlation IDs.
- Sensitive data handling is explicit and enforced.
- Retention and access are policy-compliant.

## Failure Conditions
- Stop when logs lack required incident context.
- Stop when sensitive data redaction is not reliable.
- Escalate when logging policy conflicts with compliance requirements.