OtOpcUa navigation

Fleet status

Deployment application across driver-role nodes.

Proposed UI · illustrative data. This page does not connect to a fleet.

One node needs attention. A deployment can be applied with a degraded address space. Inspect the full failure reason before considering it healthy.

Driver nodes

3 nodes · 2 applied · 1 degraded

Sample read:
Production pattern: refresh every 10 seconds

Per-node application status. Open details to read the full failure reason.
NodeRoleApplication statusApplied at (UTC)Details
driver-east-01DriverApplied · degraded21:41:58Read failure reason
driver-east-02DriverApplied21:41:57—
driver-west-01DriverApplied21:41:56—

Showing 3 of 3 sample nodes

Failure reason

driver-east-01

Applied · degraded The node runs the revision, with a partial address-space apply.

Read full illustrative failure

The configured driver could not initialize one device. Inspect node diagnostics to identify the affected driver and verify the device connection before the next deployment.

Node
driver-east-01
Applied at
2026-11-12 21:41:58 UTC
Recommended next step
Open the node's diagnostics in the production interface. This prototype contains no diagnostic endpoint.
Proposed refresh and live-data behavior

Keep the last successful reading visible when refresh fails. Show its time and a stale label. In live log pages, let operators pause row updates while reading; report connection changes without announcing every incoming row.