Monitoring
The Supra Server provides two monitoring options: a Grafana dashboard running on the server itself and cloud-based metrics viewable directly in Box. Choose the approach that fits your workflow — or use both.
| Approach | Access | Best for |
|---|---|---|
| Grafana (server-side) | http://<server-ip>:3000 | Detailed historical graphs, system resources |
| Box Monitoring card (cloud) | Device detail → Supra tab | Quick per-client metrics view from anywhere |
Grafana Dashboard (Server-Side)
Installation
- Navigate to the Supra Server device in Box.
- Go to the Scripts section (or use the Supra tab if a monitoring action is available).
- Execute the Supra Server - install-monitoring Custom Script.
- Wait for the installation to complete.
- The Grafana URL will be displayed in the script output (e.g.,
http://192.168.3.202:3000).
Accessing the Dashboard
After installation, access the monitoring dashboard at:
http://<supra-server-ip>:3000
Default credentials:
| Field | Value |
|---|---|
| Username | admin |
| Password | user-defined |
Change the default credentials after first login via the Grafana user settings.
Pre-installed Dashboard
The monitoring stack comes with a pre-installed Supra Dashboard that displays:
| Metric | Description |
|---|---|
| Stream status | Active streams and connected clients |
| Framerate | Rendering frames per second |
| Bitrate | Stream bandwidth usage |
| Rendering latency | Time from render to display |
| Rendering starts | Number of rendering session initiations |
| Process CPU usage | CPU consumption by Chromium, Supra Server Daemon, and screen sessions |
| Machine CPU & Memory | Overall system resource utilization |
Monitoring Stack Components
The monitoring solution runs as a set of containers on the Supra Server:
| Container | Purpose |
|---|---|
supra-server-monitoring-grafana | Grafana dashboard UI |
supra-server-monitoring-prometheus | Metrics collection and storage |
supra-server-monitoring-telegraf | System metrics agent |
supra-server-monitoring-node-exporter | Node-level metrics exporter |
supra-server-monitoring-process-exporter | Process-level metrics exporter |
Network Requirements
The monitoring dashboard is accessible on port 3000 of the Supra Server. Ensure this port is reachable from your management network if you need remote access to the dashboard.
Cloud Monitoring via Box
You can view real-time Supra metrics directly in Box without accessing the server's network. The Monitoring card on the Supra tab collects Prometheus metrics from the Supra Server on demand and displays per-client performance data.
Accessing the Monitoring Card
- Navigate to the Supra Server device in Box.
- Open the Supra tab.
- Scroll to the Monitoring card (visible when the Supra Server is installed).
Server Metrics
The top of the Monitoring card shows server-level totals:
| Statistic | Description |
|---|---|
| Connected Screens | Number of active screen rendering sessions |
| Connected Clients | Number of client devices currently connected |
Client Metrics Table
Below the server totals, a table lists every device in the same Location with the following columns:
| Column | Description | Format |
|---|---|---|
| Device | Device name (links to the device detail page) | Text |
| Connected | Whether the device was matched to metrics data | Yes / No tag |
| Frame Rate | Current rendering frame rate | 30 fps |
| Byte Rate | Stream bandwidth | Auto-scaled (B/s, KiB/s, MiB/s, GiB/s) |
| Latency | Rendering latency | Auto-scaled (ms, s, min) |
| Resolution | Client screen resolution | 1920 × 1080 px |
| Last Connected | When the client last connected to the Supra Server | Localized date and time |
| Last Interaction | When the client last received interaction input | Localized date and time |
If a device shows No in the Connected column, it means no matching metrics were found for that device in the latest collection. The device may be offline or not yet connected to the Supra Server.
Refreshing Metrics
- Manual refresh — Click the Refresh button in the card header to trigger a new metrics collection.
- Auto Refresh — Toggle the Auto Refresh switch to collect new metrics every 30 seconds. A countdown indicator shows the time until the next collection.
Auto Refresh is not persistent — it resets to off when you navigate away from the page or refresh the browser.
How Device Matching Works
The Supra Server identifies connected clients by a hashed device identifier. Box matches each device in the Location to its metrics by computing the same hash from the device's unique ID (DUID). Devices that cannot be matched — for example, because they are offline or not connected to the Supra Server — appear in the table without metrics data.
Raw Metrics
You can retrieve raw Prometheus metrics from the Supra Server daemon without installing the full monitoring stack by running the Supra Server - get-metrics Custom Script.
- Navigate to the Supra Server device in Box.
- Go to the Scripts section.
- Execute the Supra Server - get-metrics Custom Script.
- The script output will contain raw Prometheus metrics in text format.
The script queries the daemon's built-in metrics endpoint and returns the data as plain text. On failure (e.g., if the daemon is not running), it returns an error message and a non-zero exit code.
This script does not require the Grafana monitoring stack to be installed. It reads metrics directly from the Supra Server daemon.
Use raw metrics when you want to:
- Integrate Supra metrics into an external monitoring system (e.g., your own Prometheus or Datadog instance).
- Perform a quick health check of the Supra Server daemon.
- Collect metric snapshots for diagnostics or support requests.
Related Topics
- Supra Server — Installing and managing the Supra Server
- Telemetry — Cloud-based connection status telemetry for client devices
- Client Devices — Setting up and managing Supra on client devices
- 4K/UHD Rendering — Configure resolution (may impact server resources)
- Known Limitations — Current limitations