Collector Pit Wall
Endpoint Failure

Master Control
Redis
No rigs configured. Open Configuration to set up.
Configuration
General
Observability Cloud
Token configured
Splunk Enterprise / Cloud
Token configured
Mode
Playback Mode
Use recorded telemetry data
Collector Health
Logs
Lines
Help
  1. Open Config and set the number of rigs, enable endpoints, and enter credentials
  2. Click Deploy Configuration to save
  3. Toggle Master Control to start all collectors
  4. In the F1 25 game, set UDP Telemetry to On and configure the IP and port to match each rig
  5. Start a session — telemetry streams automatically

Each card represents a driver station. Click the driver name to edit it — names sync to Redis and are used as dimensions in telemetry data.

Speed / Lap / Track
Live race data from the F1 game
UDP
Listening port — green = receiving, amber = no data, gray = stopped
Memory
Collector process memory usage
Queue
Network backpressure indicator — see states below
Queue States
QUEUE OK
All requests flowing — no drops, inflight below 50% capacity
Q:12/50
Inflight requests ≥ 50% of max — backpressure building
3 DROP
Requests are being dropped — Splunk endpoint may be unreachable or slow
LED Indicators
Healthy Partial Error Info Inactive

Observability Cloud — sends metrics via the Splunk Ingest API. Requires a realm and access token with ingest scope.

Splunk Enterprise / Cloud — sends events via HTTP Event Collector (HEC). Requires the HEC URL and token.

Playback Mode — replays recorded telemetry data instead of live UDP. Useful for demos without the F1 game. When enabled, select a .tlm replay file for each rig from the dropdown. Files are created via the Record button and stored inside the container at telemetry_data/. Use a Docker volume mount to persist recordings across container restarts.

Deploying a new configuration stops all collectors and resets the database.

Click the Health button to open the health panel. It displays real-time telemetry statistics for all active collectors.

Metrics
Total Packets
Cumulative count of UDP packets received since the collector started
Total Data
Cumulative bytes received across all packet types
Packets/sec
Current throughput rate of incoming telemetry packets
Parse Errors
Packets that could not be decoded — shown in red if non-zero
Bandwidth Grades
Minimal / Light
Under 10 Mbps — typical for a single rig on WiFi or 4G
Moderate / Heavy
10–1000 Mbps — multiple rigs on a wired connection
Intensive / High / Saturated
Above 1 Gbps — high-volume scenarios
Views
Combined view
Shown when 2 or more collectors are active — aggregates totals across all rigs
Single collector view
Shown for individual rigs — includes uptime, per-second rates, and a breakdown of packet types received

Endpoint Check — the Config panel tests connectivity to Observability Cloud and HEC endpoints when you deploy. Status indicators show whether each endpoint is reachable.

Click the Logs button to open the log viewer. Six log sources are available: collector, supervisor, redis, gunicorn, nginx (errors), and nginx-access (request log).

Controls
Lines (50 / 100 / 200)
Number of recent log lines to display
Auto
Refreshes the log view every 5 seconds when enabled
Refresh
Manually reload the current log source
Log Forwarding

When HEC is enabled, container logs are automatically forwarded to Splunk every 5 seconds. Each source is indexed with its own sourcetype:

f1:collector — collector process logs
f1:supervisor — supervisord process manager
f1:redis — Redis server output
f1:gunicorn — Gunicorn WSGI server
f1:nginx — Nginx reverse proxy

No additional configuration is needed — forwarding activates and deactivates with HEC.