🗺️ DevOps & Cloud · Journey Playbooks

Playbook: Choose your observability stack deliberately

Vendor wired via OpenTelemetry with cardinality budgets and routing discipline.

journey~25 minDevOps EngineersSREsCloud Architects

Journey Steps

1Step 1 — Adopt structured logging that answers questions: start with "Log JSON with timestamp, level, service, route, request_id, user_id"
2How it fits together: Pick one variant per reality; exit paths matter more than features.

Commands

Install all referenced skills

$ npx skills add aniruddhaadak80/skills --skill observability-structured-logging

Tags

#playbook#journey#devops-cloud

Install this skill

$ npx skills add aniruddhaadak80/skills --skill playbook-devops-cloud-obs-stack-choice -a opencode

SKILL.md

# Playbook: Choose your observability stack deliberately

> Vendor wired via OpenTelemetry with cardinality budgets and routing discipline.

## When to Use This Skill

Vendor wired via OpenTelemetry with cardinality budgets and routing discipline.

## Steps

1. Step 1 — Adopt structured logging that answers questions: start with "Log JSON with timestamp, level, service, route, request_id, user_id"
2. How it fits together: Pick one variant per reality; exit paths matter more than features.

View source on GitHub ↗

Take retrieval-augmented answers from empty repo to evaluated production feature.

🗺️ AI Engineering·~135m

Open →

🗺️Playbook: Harden an agent before giving it toolsjourney

Ship an autonomous agent whose failure modes are cheap, visible, and reversible.

🗺️ AI Engineering·~125m

Open →

🗺️Playbook: Cut LLM costs without quality collapsejourney

Reduce monthly inference spend measurably while keeping answer quality within tolerance.

🗺️ AI Engineering·~95m

Open →