Diagnostic Playbooks
Browse available diagnostic playbooks and understand what each one checks.
Diagnostic Playbooks
Built-in playbooks the AI uses to investigate issues:
| Playbook | What it checks |
|---|---|
diag.network-connectivity | Ping gateway, DNS, VPN client |
diag.cpu-spike | Running processes, CPU history |
diag.disk-space | Disk usage per volume |
diag.service-health | Windows/Linux service status |
diag.event-log-errors | Last 50 Windows error log entries |
diag.ssl-cert | Certificate expiry and chain |
diag.printer-toner | Toner levels via SNMP |
diag.patch-status | Pending OS patches |
Run a playbook manually
Open a ticket → the Run Diagnostics panel on the ticket → select playbook → select device → Run. Output appears as an internal note within 30 seconds.
Where to go next
- Understand the whole module → How AI Autonomy Works
- Next in this module → Run a Diagnostic Playbook
- Approve or Reject Pending Actions
- Set Up Approval Workflows
- See where this fits in the bigger picture → Start Here: What Plenix Is and How It Fits Together
Was this article helpful?