Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/observability

@228d57d
Run it yourself

This skill should be used when the user asks about "observability" or "monitoring", what "metrics, logs, and traces" to collect, "health checks" (liveness/readiness), "alerting" or "on-call", "SLO/SLI" or "error budgets", the "RED" or "USE" method, "dashboards", or names a tool like "Prometheus", "Grafana", or "Datadog". Use it whenever a design has no answer to "how would we know this is broken?" or "what do we alert on?" — i.e. any time failure would be invisible until users complain, even if the user doesn't say "observability".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/observability

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersgeneric.md

≈571 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Observability — generic (vendor-neutral / self-hosted)

The default answer. Instrument with OpenTelemetry, then route to open-source backends. This stack is portable and the baseline every provider file maps against.

Service mapping (recipe → open source)

  • Instrumentation seam — OpenTelemetry SDK + Collector. One instrumentation, any backend; the thing that keeps you off lock-in.
  • Metrics + alerting — Prometheus (pull/scrape, PromQL) with Alertmanager for grouping/inhibition/routing. Long-term storage via Thanos or Mimir when a single Prometheus won't hold retention.
  • Dashboards — Grafana (queries Prometheus, Loki, and Jaeger in one pane).
  • Logs — Loki for log aggregation/query (label-indexed, cheap), or the Elasticsearch/ELK route. The full high-volume pipeline is distributed-logging.
  • Traces — Jaeger (or Tempo / Zipkin); receives OTLP spans, supports tail sampling via the Collector.

When to pick which

  • Prometheus + Grafana + Alertmanager is the near-universal metrics/alerting core.
  • Add Jaeger/Tempo only once requests cross services and you need per-hop timing.
  • Loki when you want logs in Grafana cheaply by labels; ELK when you need full-text search and rich indexing (heavier to run).

Limits / things that bite (verify against current docs)

  • Prometheus is single-node and not long-term storage by default — retention and HA need Thanos/Mimir/Cortex; plan this before cardinality grows.
  • Cardinality is the hard ceiling — series ≈ product of label values; one unbounded label OOMs the server. Govern labels, not just scrape rate.
  • Pull model needs network reachability to every /metrics target; short-lived jobs need the push-gateway.
  • Self-hosting means you run the HA, retention, and upgrades — real operational cost.

Pitfalls

  • Treating Prometheus as durable/long-term storage without Thanos/Mimir.
  • High-cardinality labels (user/request IDs) in metrics — push those to traces/logs.
  • Synchronous OTLP export blocking the app; use the Collector with a queue + drop.
  • Running ELK "because it's standard" when Loki + metrics would cover the need at a fraction of the operational load (borrowed context, not reasoning).

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts23d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill provides comprehensive architectural guidelines for implementing observability, monitoring, and alerting in distributed systems. It contains no executable code, remote dependencies, or malicious patterns.

  • Socket23d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/observability