Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Observability and Instrumentation

A production-engineering playbook for adding structured logs, RED metrics, OpenTelemetry traces, and symptom-based alerts as you build a feature.

Dev & CodingIntermediate★ 422⑂ 44AI score 8/10Last updated: Sep 12, 2026

What it does

  • Forces you to write down the 2–4 questions an on-call engineer will ask before you instrument anything, then maps each question to the right signal (log, metric, or trace).
  • Enforces structured logging with stable event names, mandatory correlation IDs, entry-point fields for shared log sinks, and a hard no-secrets/no-PII rule.
  • Applies RED metrics to every endpoint and external dependency (USE for resources) with strict cardinality rules and histograms instead of averages.
  • Covers OpenTelemetry tracing setup, symptom-based alerting with two severities, three-line runbooks, and a final step that verifies the telemetry itself in staging.

Who it's for

  • Backend, platform, and SRE/DevOps engineers shipping services to production.
  • Teams whose incident postmortems say "we couldn't tell what happened".
  • Anyone cleaning up a noisy pager or an over-cardinality metrics bill.
  • Reviewers who want to catch PRs with retries, queues, or external calls and zero telemetry.

Examples

  1. Shipping a payment retry flow: define on-call questions, emit a payment_failed structured event with provider error codes, and add a provider-latency histogram.
  2. Fixing alert fatigue: delete CPU/memory pages, replace them with error-rate > 1% for 5 min and p99 > 2s alerts, each linked to a runbook in docs/runbooks/.
  3. Taming a metrics cardinality bomb: find series labeled with user IDs or raw URLs, swap in route templates and status classes, and move the detail into logs and traces.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/aiskillstore/marketplace/HEAD/pending/addyosmani/observability-and-instrumentation/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the pending/addyosmani/observability-and-instrumentation folder from the GitHub repo aiskillstore/marketplace into my ~/.claude/skills/observability-and-instrumentation/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/aiskillstore/marketplace.git /tmp/aiskillstore && mkdir -p ~/.claude/skills && cp -r /tmp/aiskillstore/pending/addyosmani/observability-and-instrumentation ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repository into a temp folder: git clone https://github.com/aiskillstore/marketplace.git /tmp/aiskillstore
  3. Create the skills directory if needed: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r /tmp/aiskillstore/pending/addyosmani/observability-and-instrumentation ~/.claude/skills/
  5. Check whether the referenced references/observability-checklist.md exists; if not, copy it from the repo using the same relative structure.
  6. Restart Claude Code and trigger it with a prompt like "review the logging, metrics, and alerting for this service before we ship".
View source on GitHub ↗