Monitorable documentation
Monitorable monitors Linux servers. You install one agent on each server with a single command; it reports CPU, memory, disk, network, Docker containers, systemd services, and disk health to the dashboard, and alerting reaches you by email, Telegram, Discord, Slack, PagerDuty, webhook, or ntfy. The agent is a custom build of the OpenTelemetry Collector, and metrics travel as standard OTLP.
New here? Start with the Quick start — it takes an account from empty to live metrics in about five minutes:
Quick startSign in, add a server, run one install command, and see live metrics.
The component you install on each server — how to set it up and exactly what it’s allowed to do:
Install the agentGet the install command, run it as root, and confirm metrics are flowing.
Requirements & permissionsWhat the agent needs, and every privilege the install grants.
What the agent collectsEvery metric and field that leaves your server — and what never does.
Update or uninstall the agentUpgrade by re-running the install command, or remove the agent cleanly.
Metrics & panels
Section titled “Metrics & panels”What a server’s page shows and how to read it:
Host metrics panelsThe status bar, CPU/memory/disk/network panels, time ranges, and stats.
Docker containersContainers appear automatically, with alerts when one stops or turns unhealthy; CPU is per core, like docker stats.
systemd servicesA 5-minute snapshot of your services — failed units first, with an alert when one fails or keeps restarting.
Listening ports and connectionsWhich TCP ports a server listens on and how many connections each carries, with an optional alert when one disappears.
Disk health (SMART)Per-drive SMART verdicts, wearout, and errors on bare-metal servers, each with an alert rule.
Alerting
Section titled “Alerting”Templates, incidents, and where notifications go:
How alerting worksTemplates bundle rules, channels, and reminder policy; incidents fire and resolve per server.
Notification channelsEmail, Telegram, Discord, Slack, PagerDuty, webhook, or ntfy — with a test button and daily caps.
Alert rulesAll 20 rule types with defaults, limits, and exactly when each fires — and how to set one up.
Account & data
Section titled “Account & data”Signing in and how long your data is kept:
Sign in & accountPasswordless: Google, GitHub, or a one-time email link and code.
Metrics history & resolutionPer-minute detail for 35 days, hourly history for 400 — and what deletes data.
Troubleshooting
Section titled “Troubleshooting”No data appearingThe agent is installed but nothing arrives: the checks, from service state to delivery errors.
A panel is missing or emptyPanel-by-panel checks separating by-design absence from a fixable permission gap.
FAQLinux-only, OpenTelemetry-native, under 1% of a core — the short answers.