Performance Monitoring

Last validated: 2026-05-05

Use performance monitoring to answer two questions before opening logs:

Is the expected vehicle or operator online in the portal?
If it is online, is Oden receiving video, audio, control feedback, and link statistics at runtime?

Portal checks

Open the Voysys portal and go to the fleet dashboard for the account. The self-serve portal routes personal accounts through /home, vehicles through /home/vehicles, and operators through /home/operators. Team accounts use the same pages under /home/<account>.

The dashboard currently separates:

Vehicles: Vehicle-side licenses and assets, including the vehicle type and whether a matching active instance was seen.
Operators: Operator-side licenses and assets, including whether an OdenVR/Oden Player instance is active.
Projects: Portal projects that can be assigned to vehicle licenses.
Unclassified licenses: Existing portal licenses that need to be classified as vehicle or operator before they fit the new fleet model.

For an online check, look at the vehicle or operator status first. If the portal shows the asset as inactive, fix the portal, license, or service problem before spending time on video settings.

Runtime checks

When the portal shows the vehicle and operator as active, check the Oden applications.

On the vehicle side:

Confirm oden-streamer.service is running when Fleet Streamer is installed as a service.
Confirm the Streamer project loaded the expected cameras and output.
Confirm the Fleet Client plugin is authenticated.

On the operator side:

Confirm OdenVR or Oden Player is signed in or activated with the intended operator license.
Open the Remote Streamer entity and check traffic, round-trip time, packet loss, and whether video packets arrive.
Open the OCP plugin when control is enabled and check sender/receiver faults.

For the detailed in-app evidence checklist, see Diagnostics and Recording.

What to watch

Signal	Why it matters
Vehicle active in portal	Shows that the portal sees a vehicle-side application instance for the license.
Operator active in portal	Shows that the portal sees the OdenVR/Oden Player license in use.
Fleet availability	Shows whether the vehicle can be connected, monitored, or is already controlled by another session.
Remote Streamer bandwidth	Shows whether video data is arriving and whether bitrate control has room to work.
Round-trip time and packet loss	Shows whether the current link path is good enough for teleoperation.
OCP faults	Separates vehicle-side control integration problems from operator input and connection problems.
Frame-time statistics	Shows whether the computer is overloaded even when the network is healthy.

Signal

Why it matters

Vehicle active in portal

Shows that the portal sees a vehicle-side application instance for the license.

Operator active in portal

Shows that the portal sees the OdenVR/Oden Player license in use.

Fleet availability

Shows whether the vehicle can be connected, monitored, or is already controlled by another session.

Remote Streamer bandwidth

Shows whether video data is arriving and whether bitrate control has room to work.

Round-trip time and packet loss

Shows whether the current link path is good enough for teleoperation.

OCP faults

Separates vehicle-side control integration problems from operator input and connection problems.

Frame-time statistics

Shows whether the computer is overloaded even when the network is healthy.

Support notes

Capture the portal state and runtime state at the same time. A useful support snapshot includes the vehicle name, operator name, Oden versions, portal active/inactive status, Remote Streamer stats, OCP faults, and any service logs from the vehicle.