Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Set up observability for applications and infrastructure with metrics, logs, traces, and alerts.
Set up observability for applications and infrastructure with metrics, logs, traces, and alerts.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
LevelToolsSetup TimeBest ForMinimalUptimeRobot, Healthchecks.io15 minSide projects, MVPsStandardUptime Kuma, Sentry, basic Grafana1-2 hoursSmall teams, startupsProfessionalPrometheus, Grafana, Loki, Alertmanager1-2 daysProduction systemsEnterpriseDatadog, New Relic, or full OSS stackOngoingLarge-scale operations
PillarWhat It AnswersToolsMetrics"How is the system performing?"Prometheus, Grafana, DatadogLogs"What happened?"Loki, ELK, CloudWatchTraces"Why is this request slow?"Jaeger, Tempo, Sentry
"I just want to know if it's down" → UptimeRobot (free) or Uptime Kuma (self-hosted). See simple.md. "I need to debug production errors" → Sentry with your framework SDK. 5-minute setup. See apm.md. "I want real observability" → Prometheus + Grafana + Loki. See prometheus.md. "I need to centralize logs" → Loki for simple, ELK for complex queries. See logs.md.
Rate — requests per second Errors — error rate by endpoint Duration — latency (p50, p95, p99)
Utilization — CPU, memory, disk usage Saturation — queue depth, load average Errors — hardware/system errors
DoDon'tAlert on symptoms (user impact)Alert on causes (CPU high)Include runbook linkRequire investigation to understandSet appropriate severityMake everything P1Require actionAlert on "interesting" metrics Alert fatigue kills monitoring. If alerts are ignored, you have no monitoring. For alert configuration, severities, and on-call setup, see alerting.md.
SolutionMonthly Cost (small)Monthly Cost (medium)UptimeRobotFree$7Uptime Kuma$5 (VPS)$5 (VPS)SentryFree / $26$80Grafana CloudFree tier$50+Datadog$15/host$23/host + featuresSelf-hosted stack$10-20 (VPS)$50-100 (VPS)
Starting with Prometheus/Grafana when Uptime Kuma would suffice No alerting (dashboards nobody watches) Too many alerts (alert fatigue → ignored) Missing runbooks (alert fires, nobody knows what to do) Not monitoring from outside (only internal checks) Storing logs forever (cost explodes)
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.