AI diagnostics
Understand incidents faster, without guessing.
When something goes wrong, Servbyte drafts a plain-language summary of the incident from your infrastructure signals. It's designed to shorten investigation time — not to replace judgement.
AI-generated insights are assistive. Servbyte drafts a hypothesis from the signals it can see. Always verify with your own logs and dashboards before acting.
What a summary includes
Every AI diagnosis follows the same structure so on-call responders always know where to look.
What happened
A short natural-language description of the observed behavior — e.g., 'API host web-03 experienced a sustained 8-minute CPU saturation.'
When it started
The first metric sample that crossed threshold or diverged from the baseline, with a precise UTC timestamp.
What was affected
The specific hosts, services, and containers whose telemetry moved with the incident.
Likely cause
Correlated signals: memory pressure, disk I/O spike, restart loop, a recent deploy marker, or an unusual traffic pattern.
Suggested next steps
Concrete checks to run — commands, logs to review, dashboards to open. Always assistive, never automated remediation.
Signals in
Telemetry streams in, a summary comes out.
What it correlates
Servbyte only reasons about infrastructure signals it already collects — nothing more.
Metric signals
CPU, memory, disk, network, load, and per-service resource usage across the affected hosts.
Log signals
Error-rate and restart signals from systemd units and container runtimes — line counts and severity, not payloads.
Recent deploy markers
Optional deploy events you send via the Servbyte API, correlated to the incident window.
Example diagnosis
A representative draft summary — as rendered inside the Servbyte dashboard.
// Draft — verify before acting
What: Sustained CPU saturation on web-03.
Started: 2026-07-28 14:22:10 UTC (~8m).
Affected: web-03, nginx.service.
Likely cause: Memory pressure preceded CPU spike; a deploy marker arrived 90s prior.
Next steps: Check the deploy diff, review journalctl -u nginx -n 200, and inspect worker restart counts.
Which plans include AI diagnostics
- Pro — AI diagnoses on active incidents.
- Team — AI diagnoses, weekly reports, and auto-drafted postmortems.
- Hobby — not included.
Data boundary
Servbyte reasons only about infrastructure signals the agent already collects: host and service telemetry, restart counts, error-log line rates, and optional deploy markers you send via the API.
It never reads your application source, request bodies, database rows, or end-user data.
Get AI-assisted incident summaries
Included on Pro and Team. 14-day free trial, no credit card.