Add structured logs, health endpoints, and persisted failure state to long-running code.
npx skills add https://github.com/GregM1991/skills --skill observability-gregm1991
Please help me install this Agent Skill. Skill: observability Source: https://github.com/GregM1991/skills/tree/main/skills/observability Command: npx skills add https://github.com/GregM1991/skills --skill observability-gregm1991
High-intent search queries and answers about installing and using this skill.
Log decisions, not activity: emit one structured event per decision point with the values that drove the choice, such as {event: "unit-dispatched", reason: "pending"}. Avoid uniform entry/exit logging, which buries signal in noise.
Structured logging emits one machine-readable event per line with fields like ts, event, and domain-specific values instead of prose strings. JSONL output is greppable and filterable, so a future debugger can query exactly what happened.
Persist failure state atomically to a known location such as runtime/last-error.json with the error, stack, and retry count, and expose a cheap health endpoint or status file returning healthy, degraded, or down. Never swallow errors in an empty catch block.
Ship only the 3-5 counters that drive alerts, such as requests, errors, and active jobs. A metrics empire of hundreds of unread series costs CPU and disk without helping anyone diagnose a problem at 3am.
Avoid logging inside tight hot loops, where you should sample or aggregate instead, and remove temporary debug lines before shipping. Keep only decision-point logs, persisted failure state, health surfaces, and explicit failure modes.
yeeehaoooDefine retry policies with exponential backoff and circuit breakers for .NET applications.
webrix-aiConfigure incident alerting workflows with Slack and Grafana integrations.
Liquid-Protocol-OpsAnalyze memory cron-state data and logs to report skill health statuses.
BagelHoleConfigure Datadog agents, integrations, logs, tracing, metrics, dashboards, and alerts.
