Incident playbooks
Playbooks are how mttrly acts on a server: predefined, scoped scripts in the agent — 80+ built in, with 50 read-only diagnostics and 30 approve-required actions — combined into diagnostic recipes for common incidents. The guides below take the most frequent incidents and show both paths: how to fix each one manually over SSH, and how mttrly runs the same triage from chat or an AI IDE, with every state-changing fix behind an explicit human approval.
Linux server disk is full
What to check when df shows 100%, which cleanup targets are safe, and how the disk-full recipe finds them — with cleanup behind an explicit approval.
Website is down
A fixed diagnosis order — ports, nginx config test, SSL, logs — and how the website-down recipe runs it in one pass, with restarts behind approval.
Detection tools tell you something is wrong. mttrly is the agent on your server that diagnoses the incident and prepares the fix — read-only diagnostics run freely, and anything that changes server state waits for your approval. See how mttrly compares to monitoring tools or how teams manage a VPS without raw SSH.
Put the playbooks on your server
Connect a server in a few minutes. Free monitoring and read-only diagnostics to start; approval-gated remediation when you want it.