Skip to content

IZI Monitoring — Real-Time PC Health Dashboard

IZI Monitoring — Real-Time PC Health Dashboard

Section titled “IZI Monitoring — Real-Time PC Health Dashboard”

IZI Monitoring is an optional add-on (additional module) to IZI CRM that gives every administrator a live technical view of each PC in the venue. The dashboard shows CPU load, RAM usage, hardware temperatures, network traffic, and disk activity — updating continuously without a page refresh. An admin can spot an anomaly before the guest has time to complain. When any metric crosses its configured threshold, the system fires a Telegram alert directly to the sysadmin’s or manager’s phone. Activating IZI Monitoring requires the IZI client already installed on each PC and a one-time activation by the IZI support team — it cannot be enabled from CRM settings independently.

How IZI Monitoring differs from CRM analytics

Section titled “How IZI Monitoring differs from CRM analytics”

IZI CRM analytics surfaces business metrics: revenue, sessions, ARPU, top-up bonuses, tariff utilization. IZI Monitoring is an entirely separate layer — the live technical health of your hardware right now.

DimensionIZI CRM AnalyticsIZI Monitoring
What it measuresBusiness KPIsHardware state
Time horizonHistorical periodsReal time + 24 h history
Primary audienceOwner, managerSysadmin, manager
AlertsNoneTelegram alerts
Included in base planYesPaid add-on, activated by support

Together the two tools provide a complete picture: analytics explains how the club earns, monitoring ensures the machines don’t fail at peak hours.

The dashboard opens inside the club section of CRM and is accessible to users with the MONITORING_READ permission. Each connected device appears as a row with live readings.

MetricWhat it means
CPU %Processor utilization in real time
RAM %Share of occupied system memory
CPU / GPU TempDegrees Celsius from on-chip sensors
Network ↓↑Inbound and outbound traffic in Mbps
DiskRead/write activity level

Rows where any metric exceeds the configured threshold are highlighted — in a large venue you don’t need to scroll the whole table; the problem PC stands out immediately. Clicking a row opens a 24-hour history chart, useful for distinguishing a one-off spike from a trend that has been building all evening.

If monitoring has not been activated for a club, the CRM shows a “Monitoring not connected” message with a prompt to contact IZI support.

Activation is a one-time process that typically takes one business day.

  1. Confirm the IZI client is installed on each PC and the device appears in the Devices section with an Active status.
  2. Contact IZI support and request monitoring activation — for the whole club, specific machines, or the entire organization.
  3. After activation, the Monitoring tab becomes clickable in the CRM navigation.

For a club network, monitoring can be enabled organization-wide or per club. The aggregated CRM view shows how many PCs are being monitored per club (monitoredPcCount) and the total device count (totalPcCount).

Telegram alerts are the core operational benefit of monitoring: they arrive even when the CRM is closed, including overnight. Configure them in the Alert Settings section of CRM.

  1. Open Telegram and find @BotFather.
  2. Send the /newbot command, choose a name and a username.
  3. Copy the API Token that BotFather provides — you’ll need it in Step 3.
  4. Open a conversation with your new bot and tap Start to activate it.

Step 2. Prepare the destination chat or channel

Section titled “Step 2. Prepare the destination chat or channel”
  1. Create a group or channel for alerts (or use an existing one).
  2. Add your new bot to that chat.
  3. If the destination is a channel, grant the bot Administrator rights — otherwise it cannot post messages.
  4. Get the Chat ID: open web.telegram.org, navigate to the target chat — the URL will contain #-987654321. Everything after /# is your Chat ID (keep the minus sign if present).

In Alert Settings, click Connect and fill in the fields:

FieldWhat to enterLimit
Bot tokenAPI Token from @BotFatherup to 120 chars
Chat IDID of the chat to receive alertsup to 32 chars
Alert languageEnglish or Russian

Click Save. Alerts will start arriving in the chosen chat. To disconnect the bot, use the Reset button in the same settings panel.

Each notification includes:

  • the PC identifier (PC#N),
  • a description of the issue with the exact metric value that triggered it,
  • a collapsible recommendation for resolving the problem.

The same alert for the same PC is not re-sent for 24 hours — built-in deduplication prevents notification spam. If you need to reset deduplication earlier (for example, after manually fixing the problem), this can be done from CRM.

When you open the dashboard, prioritize by guest impact:

  1. Highlighted rows (threshold exceeded) — act immediately.
  2. CPU / GPU temperature — overheating is the most common precursor to a freeze.
  3. RAM close to the threshold — processes begin swapping, games start stuttering.
  4. Unusually high network traffic on a single machine — possible background update or rogue process.

If several machines simultaneously show high network load, check whether a mass game update is running: Steam and Epic sometimes start downloads across the whole venue at once.

Monitoring permissions in IZI CRM are controlled by two club-level roles:

PermissionWhat it grants
MONITORING_READView the dashboard and live metrics
MONITORING_MANAGEConfigure alert thresholds and Telegram bot

This separation lets you give a sysadmin read-only access while the manager retains full control over alert configuration.

Monitoring and IZI Boot are designed to work in tandem. When a device starts behaving erratically — persistent temperature peaks, frequent game crashes — rolling it back to a clean image via IZI Boot is usually faster than manual on-site diagnostics. Monitoring surfaces the problem; IZI Boot resolves it without requiring a sysadmin to be physically present.

For a step-by-step guide to configuring thresholds, reading history charts, and diagnosing common anomalies, see Real-time PC monitoring.

Frequently asked questions

What is IZI Monitoring?

IZI Monitoring is an optional add-on to IZI CRM that adds a real-time hardware health dashboard for every PC in your venue: CPU load, memory usage, temperatures, network traffic, and disk activity — all updating live, without a page refresh. When any metric crosses a configured threshold, the system sends an alert to a Telegram chat of your choice.

How does IZI Monitoring differ from IZI CRM analytics?

IZI CRM analytics covers business metrics — revenue, sessions, ARPU, bonuses, tariff load. IZI Monitoring is a completely separate layer: the live technical state of your hardware right now. Analytics helps you run the business; Monitoring helps you prevent hardware failures before they upset a paying guest.

How do I activate IZI Monitoring?

Monitoring is activated by the IZI support team, not through CRM settings on your own. First make sure the IZI client is installed on each PC and the device appears as Active in the Devices section. After the IZI team activates it, the Monitoring tab becomes clickable in the CRM navigation. Activation normally takes one business day.

Which metrics does the Monitoring dashboard show?

For each connected device the dashboard displays: CPU utilization (%), RAM usage (%), CPU and GPU temperature, inbound and outbound network traffic (Mbps), and disk read/write activity. Rows where any metric exceeds its configured threshold are highlighted, so a problem machine is visible at a glance even in a large venue.

How do I set up Telegram alert notifications in IZI Monitoring?

Open the Alert Settings tab inside the Monitoring section of CRM. Connect a Telegram bot by entering the bot token (up to 120 characters) and the Chat ID of the group, channel, or private chat that should receive alerts (up to 32 characters). Select the notification language — English or Russian — then save. Alerts will start arriving in that chat immediately.

What does a Telegram alert message contain?

Each notification includes the PC identifier (PC#N), a description of the issue with the exact metric value that triggered it, and a recommendation for resolving it. The same alert for the same PC is not repeated for 24 hours — built-in deduplication prevents notification spam.

Can I enable monitoring for my entire club network at once?

Yes. Monitoring can be activated at the organization level (all clubs) or per individual club. The CRM aggregated view shows how many PCs are being monitored in each club and the total device count across your network.

Is IZI Monitoring included in the base IZI CRM subscription?

No. IZI Monitoring is a paid add-on on top of the base IZI CRM subscription. Pricing depends on the number of clubs and PCs under observation — contact the IZI team for current terms.

What should I do if the Telegram bot stops sending alerts?

Check that the bot has not been removed from the chat and is not blocked. Open Alert Settings in CRM — if the bot token was revoked or the bot was removed from the chat, the system automatically resets the configuration. Reconnect the bot using the Connect button and re-enter the token and Chat ID.

Can I see metric history for a single PC?

Yes. Click any device row in the dashboard to open a chart showing that device's metric history over the past 24 hours. This lets you tell whether a temperature spike was a brief peak or has been building up all evening.

Does monitoring keep working when the CRM tab is closed?

Yes. The agent installed on each PC sends metrics continuously, independent of whether the CRM is open. Telegram alerts arrive at any time of day. The dashboard shows the current live state whenever you open it.