Real-time PC Monitoring

Real-time PC Monitoring

The Monitoring tab inside Settings → Devices displays live metrics for every PC in the hall: CPU load, memory usage, network activity, hardware temperatures. Data updates without a page refresh — staff spot anomalies on screen before a player reports them. Telegram alerts fire even at night when the club is closed, so the admin can respond before opening, not after.

What the dashboard shows

Each device (name, zone) appears as a row with live readings:

Metric	What it means
CPU %	Processor load in real time
RAM %	Share of memory in use
CPU / GPU temp	Degrees Celsius from hardware sensors
Network ↓↑	Inbound and outbound traffic (Mbit/s)
Disk	Read/write activity

Rows with a metric above its threshold are highlighted — no need to scroll the full table in a large hall.

Clicking a device opens a 24-hour history graph per metric. Useful for distinguishing a one-off spike from a trend building all evening.

How to enable monitoring

Monitoring is activated via IZI Technical Support — not through CRM settings on your own. It’s a one-time operation:

1. Confirm the IZI client is installed and the device is paired — it must appear in Settings → Devices with status Active.
2. Contact support and request monitoring to be enabled for your club (or specific machines).
3. After activation, the Monitoring tab becomes clickable in the Devices section navigation.

For club networks, monitoring can be enabled for the entire organisation or per club.

Telegram alerts: setting thresholds

After monitoring is active, configure thresholds — the values above which, held for a defined duration, the system treats as an anomaly:

• CPU > threshold% for N minutes — filters out short spikes when games launch. For example: CPU > 95% for more than 2 minutes.
• CPU / GPU temp > threshold°C — hardware overheating. For example: temperature > 85°C.
• RAM > threshold% — memory pressure; processes start swapping.

Notifications arrive in the admin’s Telegram with: device name, metric value, time the anomaly started. When the metric returns to normal, a resolution notification follows.

Start with conservative thresholds and adjust after the first week. Frequent false alerts → raise the threshold. Missed incidents → lower it.

What to check first

Priority order when opening the dashboard:

1. Red rows (threshold exceeded) — needs action now
2. Temperature — overheating most often precedes a crash
3. RAM near threshold — processes may start swapping, games stutter
4. Unusually high network traffic on one machine — likely a background update or malware

If multiple machines simultaneously spike on network — check whether a game is auto-updating: Steam and Epic sometimes push updates to the whole hall at once.

Relationship with IZI Boot

Monitoring and IZI Boot work together. If a device shows persistent anomalies (constant CPU peaks, crashes), resetting it to the clean disk image via IZI Boot is faster than manual diagnosis.

See also

• IZI Boot overview
• Connecting PCs to IZI
• Hall real-time view

FAQ