Skip to content
F1 2025 Collector

F1 2025 Data Collector

The F1 2025 Collector receives UDPThe network protocol F1 25 uses to send telemetry packets to the collector. Each rig sends to the collector's IP address and its assigned UDP port. telemetry from up to four racing rigs and sends it to Splunk Enterprise or Splunk Cloud through HTTP Event Collector (HECSplunk's HTTP endpoint for receiving event data. The collector uses a HEC URL and token to send full telemetry to Splunk Enterprise or Splunk Cloud.). It can also send a focused set of real-time metrics to Splunk Observability Cloud.

F1 2025 Collector

The collector is a single Go application. One process serves the web interface, listens on every rig’s UDP port, and delivers to both destinations, so there are no separate listener, queue, or database services to manage.

The default setup uses one rig on UDP port 20777. Additional rigs can be enabled from the collector when an event needs them.

Two views

ViewPathPurpose
Collector/The operator screen. Master Control, rig cards, driver names, recording, configuration, health, and logs.
Pit Wall/pitwallA broadcast-style live telemetry view for a single rig, suitable for a display screen behind the booth.

Choose your setup

This is how most events run. Your Show instance already has the collector installed, running, and configured for HEC. Do not replace the HEC URL or token unless your event administrator asks you to.

  1. Open http://<your-show-host>.splunk.show:81.
  2. Confirm an Event Name is set under Config → General.
  3. Configure only your Splunk Observability Cloud destination, if you are using it.
  4. Select Deploy Configuration, then turn on Master Control.
  5. Copy the collector’s public address from the header into F1 25 and use UDP port 20777 for the first rig.
  6. Enter the driver’s name on the rig card before their race.

Event workflow

  1. Open Config, set the number of rigs and an Event Name, and enable the destinations you need.
  2. Select Deploy Configuration. This writes the configuration file and stops any running collectors.
  3. Turn on Master Control. The collector validates every enabled destination before it starts; a failed check prevents startup and shows the reason.
  4. Configure each game to use the collector’s address and that rig’s UDP port.
  5. Enter the driver’s name on the correct rig card before their race.
  6. Run the event. When F1 25 sends Final Classification, the collector marks the rig Race complete and emits a SessionCompleted summary containing the session’s fastest lap.
  7. If Final Classification never arrives, the collector falls back to Session Ended after a 60-second grace period and publishes the summary from cached data.

Test before guests arrive

Run one complete short race, including the results screen, before the event. This checks UDP reception, destination delivery, and automatic session completion in one pass.

Next steps

The Collector page
Understand rig cards, driver names, recording and status.
Configure the collector
Set your event name, destinations and playback mode.
Connect F1 25
Point each racing rig at the right address and UDP port.
Run an event
Manage drivers, recordings and race completion.
Use the Pit Wall
Show a single rig’s live telemetry on a booth display.
Monitor and troubleshoot
Check health, read logs and diagnose common problems.
Explore your dashboards
View telemetry in Splunk and Observability Cloud.