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.

referencesprovidersaws.md

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

Observability — AWS

Service mapping

  • CloudWatch Metrics — managed metrics + dashboards + CloudWatch Alarms for alerting. The default; integrates with most AWS services out of the box.
  • CloudWatch Logs — managed log ingestion/query (Logs Insights). The pipeline concern is distributed-logging; here it's the metrics/alarm + log-metric-filter side.
  • X-Ray — managed distributed tracing; OTLP via the ADOT (AWS Distro for OpenTelemetry) Collector.
  • Amazon Managed Service for Prometheus (AMP) + Managed Grafana — run the generic Prometheus/Grafana stack without self-hosting; pick this to stay PromQL-portable instead of CloudWatch-native.
  • CloudWatch Synthetics / Route 53 health checks — synthetic + external liveness probing (health-check gating is load-balancing).

When to pick which

  • CloudWatch for native, low-setup metrics+alarms across AWS services.
  • AMP + Managed Grafana when you want the generic recipe managed (portability, PromQL, existing dashboards).
  • X-Ray for tracing if you're CloudWatch-native; ADOT keeps you OTel-portable.

Limits / things that bite (verify against current docs)

  • CloudWatch custom-metric and high-cardinality dimension costs add up fast — each unique dimension combination is a billable custom metric.
  • Standard CloudWatch metric granularity is 1-minute (high-resolution down to 1s costs more) — alerting reaction time is bounded by this.
  • PutMetricData / API throttling under bursty custom-metric publishing.
  • X-Ray sampling is configured separately; default rules may under-sample errors.

Pitfalls

  • Emitting high-cardinality CloudWatch dimensions (user/request IDs) — cost explosion; keep those in logs/traces.
  • Assuming 1-minute metrics are fast enough for tight SLO burn alerts.
  • CloudWatch-native lock-in: dashboards/alarms don't port; AMP+Grafana avoids this.
  • Forgetting cross-account/cross-region aggregation cost when centralizing telemetry.

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