Monitoring and Maintenance
Use Engine for live status and host monitoring for long-term history and alerts.
Monitor
| Page | Use |
|---|---|
| System Overview | CPU, memory, network, disk, servers, and connections |
| Servers | Health, uptime, resources, connections, and license usage |
| Server Usage | CPU, memory, network, Intel GPU, and NVIDIA GPU charts |
| Connections | Active playback by server |
| System Log | Messages from reachable servers |
| Audit Log | Management changes and who made them |
Filter Logs
Press Enter to apply a case-insensitive search.
| Search | Result |
|---|---|
text | Show matching lines |
!text | Hide matching lines |
| `!(text | |
!(text && other) | Hide lines containing both terms |
Search terms are literal text. The count shows visible/total lines. Copy copies only lines matching the submitted search and level filter.
Engine 1.0+
Resource Pressure
Compare CPU, memory, disk, GPU, connections, and license usage together. Use Tools → Capacity & Reliability for controlled testing; a short spike does not establish capacity.
Under high CPU load, Engine delays new Stream and Adapter starts without stopping running processes. Starts resume after resources recover. The configured Stream Interval still applies. Check logs for waiting starts and recovery status.
Changed in Engine 1.0+
Maintenance
- Download a database backup.
- Open Settings → System Settings → Management Maintenance.
- Set the UTC window and reason. Test SMTP before enabling email.
- Drain traffic separately if the work affects playback.
- Make the change, verify services, and end maintenance.
Maintenance Mode controls management access. It does not drain streams or stop playback.
Incident Data
Record timestamps, affected objects and servers, resources, license status, logs, protocol errors, and the last change.
Remove passwords, tokens, playback credentials, private keys, and full license content before sharing logs.
Embedded Docker Commands
As root, use web docker to manage this Engine installation’s containers. Arguments after docker are passed unchanged to the Docker client.
bin/web docker ps -a
bin/web docker logs --tail 200 bgutil-ytdlp-pot-provider
bin/web docker exec -it CONTAINER COMMANDManage the embedded daemon:
bin/web docker-daemon status
bin/web docker-daemon start
bin/web docker-daemon stop
bin/web docker-daemon restartDocker access permits host-level changes. Do not let untrusted users run these commands or expose arbitrary Docker commands through an HTTP endpoint.