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.

referencesprovidersazure.md

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

Observability — Azure

Service mapping

  • Azure Monitor — the umbrella: metrics, Metric Alerts, dashboards, and autoscale signals.
  • Application Insights — APM: request RED metrics, distributed tracing, dependency maps, and live metrics. Native OpenTelemetry export is supported.
  • Log Analytics (Kusto/KQL) — the log + query store behind Azure Monitor; the high-volume pipeline concern is distributed-logging.
  • Azure Managed Grafana + Azure Monitor managed service for Prometheus — run the generic PromQL/Grafana stack managed, for portability.
  • Health probes — App Service / AKS liveness+readiness; gating is load-balancing.

When to pick which

  • Application Insights when the app is .NET/Azure-centric — richest auto-instrumentation and dependency tracing with least effort.
  • Azure Monitor managed Prometheus + Managed Grafana to keep the generic recipe and PromQL portability.
  • Log Analytics/KQL when you need powerful ad-hoc log querying.

Limits / things that bite (verify against current docs)

  • Application Insights samples telemetry by default (adaptive sampling) — great for cost, but verify errors/slow requests aren't being dropped.
  • Log Analytics ingestion + retention is the main cost driver; data-cap and retention tiers change the bill sharply.
  • Metric Alerts evaluation frequency and granularity bound how fast an SLO burn is detected.
  • KQL has query limits/timeouts on large windows.

Pitfalls

  • Trusting default adaptive sampling for SLO-critical signals without checking it.
  • High-cardinality custom dimensions inflating Log Analytics cost.
  • Lock-in to App Insights SDKs/KQL dashboards — use the OpenTelemetry exporter and managed Prometheus/Grafana to stay portable.
  • Conflating Log Analytics retention with metrics retention (different knobs/costs).

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