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.

referencesprovidersgcp.md

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

Observability — GCP

Service mapping

  • Cloud Monitoring (formerly Stackdriver) — managed metrics, dashboards, alerting policies, and SLO + error-budget objects as first-class features (define an SLI/SLO and burn-rate alerts natively).
  • Cloud Trace — managed distributed tracing; OTLP/OpenTelemetry export.
  • Cloud Logging — managed log ingestion/query + log-based metrics; the high-volume pipeline concern is distributed-logging.
  • Managed Service for Prometheus + Managed Grafana — run the generic PromQL stack managed (GMP auto-collects from GKE), for portability.
  • GKE/Cloud Run health checks — liveness+readiness; gating is load-balancing.

When to pick which

  • Cloud Monitoring when you want native SLOs/error budgets and burn-rate alerts without building them — its standout feature.
  • Managed Service for Prometheus on GKE for PromQL portability with managed scaling.
  • Cloud Trace for low-effort tracing on GCP-hosted services via OTel.

Limits / things that bite (verify against current docs)

  • Cardinality / active-time-series limits per metric — unbounded labels hit ingestion limits and cost.
  • Cloud Logging ingestion + retention is the main cost driver; log-based metrics add cost on top.
  • Alerting policy evaluation period bounds detection latency for SLO burns.
  • Trace sampling is configurable; defaults may under-sample errors.

Pitfalls

  • High-cardinality metric labels hitting per-metric time-series limits.
  • Building custom SLO tooling when Cloud Monitoring's native SLOs already do it.
  • Lock-in to Cloud Monitoring dashboards/alerting — OTel + managed Prometheus/Grafana keeps you portable.
  • Forgetting log-based metric cost when deriving metrics from high-volume logs.

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