← Better StackCONTENT HISTORY
WHAT CHANGED
Update to Better Stack
Snapshot Nov 11, 2026 · 06:08 UTC · version 1.1.3
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Better Stack and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Quick health assessment of servers or services (databases, webservers) from their Better Stack telemetry. Checks metrics, logs, dependencies for anomalies. Use for \"how is Nginx and Redis doing?\" questions, not incident diagnosis.",
"included_files": [],
"name": "health-check",
"skill_md_contents": "---\nname: health-check\ndescription: Quick health assessment of servers or services (databases, webservers) from their Better Stack telemetry. Checks metrics, logs, dependencies for anomalies. Use for \"how is Nginx and Redis doing?\" questions, not incident diagnosis.\n---\n\n# Health check of service\n\nApplies to full servers or specific services (e.g., database, Redis, webserver). Prefer charts (`render_chart`) when presenting results - show a chart and a short comment, e.g. how CPU or memory is doing.\n\n## Step 1: Find the source\n\nCall `sources` to find the server's or service's sources, then `source` for each: its platform, its services and which data (logs, spans, metrics) it has. Keep progress notes short while you collect data.\n\n## Default Parameters\n\n- **Time window:** Last 3 hours (unless user specifies otherwise)\n\n## What to Check\n\n### 1. Metrics Anomalies\n\n- Resource saturation spikes (CPU, memory, disk, network)\n- Latency increases for certain services (p50/p95/p99)\n- Error rate changes\n- Throughput drops\n\nCompare current values against the 3-hour baseline. Flag deviations.\n\n### 2. Log Distribution\n\nQuery log counts by level over time:\n\n- Sudden increase in error/warn logs?\n- Drop in info logs (service stopped logging)?\n- New log patterns appearing?\n- Is there a spike in logs count by any level?\n\nGroup by `_pattern` (the message with IDs and numbers stripped) to see which kinds of lines are new or spiking; `query_help` has the syntax.\n\n### 3. Dependencies\n\nFrom spans (`spans-query`) or, on a Collector source, the requests-by-destination queries in `collector-queries`, check:\n\n- Request rate, error rate and latency between services\n- Dependencies showing elevated error rates\n- Latency spikes between services\n\n## Output\n\nProvide a simple overview of system's health, show visualizations about key metrics and point out potential issues and your finding.\n\nFor each key metric (load, memory, disk, network, ...), repeat this rhythm:\n\n1. Write the `### <Metric name>` heading\n2. Call `render_chart` with that metric's query (a real tool call; writing the tool's name in text renders nothing)\n3. Write 1-2 sentences interpreting what the chart shows\n\nChart each metric once, in the summary, not while collecting data. One chart at a time: chart, then its comment, then the next heading. Never a wall of text describing charts that were never rendered.\n\n## Collector sources\n\nWhen `source` reports platform Collector, load `collector-queries`: it carries the proven host queries (CPU, memory, load, disk, network, pressure) and the per-container pass (usage against limits, throttling, pressure, OOM kills, restarts) that host averages hide, plus the \"keeping up\" rubric for the verdict. Compare the 3-hour window against the same window a day earlier before calling a level normal. Ratios stay 0-1 with `unit: \"percent\"`; bytes stay raw with `B_iec`. Syntax: `metrics-query`.\n\n## If Anomalies Found\n\n1. Report findings with specifics (timestamps, values)\n2. Ask user: \"Want me to investigate deeper?\"\n3. If yes → load the `investigate-incident` skill and continue\n"
}SHA-256 of public snapshot: 18da3c384af74032e06f3b5bf23f3e767003d6823af166f77db2022ead94fc4d