Monitor Page
The Monitor page is the technical health dashboard for Falcon Play. It shows sockets, bandwidth, heartbeat, CPU temperature, disk, memory, playlists, workers, external rundowns, data folders, and Media Server state.
Screenshot is coming soon...
What you will learn
- Which health indicators matter during production.
- How to inspect connected clients and server load.
- How Media Server scan state affects Director.
Recommended workflow
- Open Monitor from the dashboard.
- Check socket connection and connected client count.
- Review heartbeat and bandwidth for performance issues.
- Check disk and RAM before long productions.
- Inspect Media Server scan state when media is missing.
- Use worker and external rundown tables for deeper diagnosis.
Buttons, fields, and controls
| Control | What it does | When to use it |
|---|---|---|
| Socket | Shows connection to server. | Use as first health indicator. |
| Connected clients | Lists connected Falcon Play clients. | Use to find stale or missing clients. |
| Bandwidth | Shows throughput and recent events. | Use when network load is suspected. |
| Heartbeat | Shows server tick timing. | Use to detect performance stalls. |
| CPU temperature | Shows system temperature. | Use on production machines under load. |
| Disk usage | Shows total, used, and available disk. | Use before uploads and recordings. |
| RAM / heap | Shows system and process memory. | Use to detect memory pressure. |
| Playlist stats | Shows rundown/cache state. | Use when rundowns do not update. |
| Workers | Shows background worker status. | Use for scan/export/thumbnail tasks. |
| Media Server section | Shows file scan, counts, thumbnails, and jobs. | Use when media is missing or stale. |
Best practices
- Check Monitor before large uploads or long live shows.
- Watch disk availability when media workflows are heavy.
- Use connected clients to diagnose which machine owns a workflow.
Troubleshooting
| Symptom | Likely cause | What to check |
|---|---|---|
| Heartbeat spikes | Server is under load or blocked by work. | Check workers, uploads, and system resources. |
| Media counts are wrong | Scan is still running or failed. | Check Media Server scan status. |
| Many disconnected clients | Network instability or stale browser sessions. | Close unused clients and inspect network. |
Screenshot is coming soon...