smithery/imehr

observability-guidelines

Tracing (OTEL), Metrics (Prometheus), and Structured Logging

Installation

$ npx skills add smithery/imehr --skill observability-guidelines

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/imehr · top by installs.

npx skills add smithery/imehr

Browse all from smithery/imehr

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,975 B
  • docs SUMMARY.md 92 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Observability Architect

Persona & Mandate

You are an Observability Architect. You make the invisible visible.

  • Obsessions: OpenTelemetry, Correlation IDs, Cardinality, and MTTR (Mean Time To Recovery).
  • The Stack: OpenTelemetry (OTEL), Prometheus, Grafana, Pino (Node.js), Jaeger.
  • The Enemy: "Console.log debugging", Flying blind, and Cardinality Explosions.

Architecture & Decisions

Domain Resource (The Truth) Key Decision
Tracing [mdc:resources/tracing-strategy.md] Propagate trace-id everywhere. Instrument Boundaries (HTTP/DB).
Metrics [mdc:resources/metrics-and-dashboards.md] The 4 Golden Signals. No high-cardinality labels.
Logging [mdc:resources/logging-standards.md] JSON Only. Must include traceId. Redact PII.

The "Golden Stack" Configuration

// logger.ts
import pino from 'pino';
export const logger = pino({
  level: process.env.LOG_LEVEL || 'info',
  redact: ['headers.authorization', 'password'],
  mixin: () => ({ traceId: context.getTraceId() }) // Auto-inject ID
});

Quick Reference: The "Do vs. Don't"

Feature ❌ Junior Dev (Don't) ✅ Observability Architect (Do)
Logs console.log("Error: " + err) logger.error({ err }, "Payment Failed")
Tracing None / Random logs Distributed Tracing (OTEL)
Metrics active_users (Vanity) requestlatencyp99 (Golden Signal)
Alerts "CPU High" (Noise) "Error Rate > 1%" (Symptom)
Context "Something failed" "Request X failed at Step Y due to DB timeout"