Monitoring and Maintenance
Monitoring and Maintenance
Use Engine pages for live status and host monitoring for long-term history and alerts.
Monitor
| Page | Use |
|---|---|
| System Overview | CPU, memory, network, disk, server, and connection summary |
| Servers | Health, uptime, RPC, resources, connections, and license usage |
| Server Usage | Per-CPU, memory, network, Intel GPU, and NVIDIA GPU charts |
| Connections | Active playback sessions and selected server |
| System Log | Engine messages from reachable servers |
| Audit Log | Management changes and actor information |
Read CPU, memory, network, disk, GPU, connections, and license limits together. A short spike is not a capacity result; use System → Capacity & Reliability for controlled testing.
Maintenance
- Download a database backup.
- Open Settings → System Settings → Management Maintenance.
- Enter the UTC window and reason; test SMTP before enabling email.
- Drain traffic separately when the operation affects playback.
- Perform the change, verify the required functions, and end maintenance.
Maintenance Mode controls management access; it does not drain streams or stop playback.
Incident Data
Record exact timestamps, affected object/server IDs, resource and license state, Engine logs, systemd journal entries, protocol/status, and the last change. Remove passwords, tokens, playback credentials, private keys, and full license content before sharing logs.