NEXUS WORKBENCH

See the system,
not just the traffic.

A participant starts late. An endpoint does not match. A deadline is missed. Two components are individually healthy, yet the system they form is not. Understanding that requires more than seeing packets.

Observes without joining the system

Nexus Workbench analysing a system of mixed DDS implementations Workbench sits at the centre, passively analysing systems built on Nexus and on any other standards-compliant DDS or RTPS implementation. NEXUS THIRD-PARTY DDS OPEN-SOURCE DDS EMBEDDED DDS ANY RTPS YOUR SYSTEM
WHY IT EXISTS

Every tool shows a piece.
None shows the system.

Network tools

Show packets.

Application logs

Show what one process believes happened.

DDS® admin tools

Show the entities currently visible to a participant.

Each perspective is useful. None represents the whole. Workbench reconstructs the larger picture by observing the interactions between participants — moving engineers from “what happened on the network?” to “what happened in the system?”

PASSIVE BY DESIGN

Observability should not change
the behaviour being observed.

Workbench observes RTPS traffic and reconstructs the DDS environment without becoming another participant. Participants, endpoints, topics, discovery activity and data flows all emerge from what it sees.

A view of the system from the outside — with no instrumentation threaded through the application, and nothing added to the environment simply in order to understand it.

FROM PACKETS TO BEHAVIOUR

Packets are evidence.
System behaviour is the story.

Most engineering questions start higher than the wire. Begin with the operational question and go deeper only when you need to.

  1. SystemDid it discover correctly?
  2. ParticipantWhich were present when it happened?
  3. EndpointWhy didn’t these two communicate?
  4. TopicWhen did this begin publishing?
  5. DataIs it arriving at the expected rate?
  6. PacketWhat exactly went over the wire?
AS IT EVOLVES

A distributed system is not a static diagram.

Participants appear and disappear. Endpoints are discovered. Relationships form. QoS determines who can talk to whom. Failures emerge over time.

System views reveal the current topology. Discovery views show how it formed. Timelines expose when participants appeared. Matching diagnostics explain why expected relationships did — or did not — form.

RELATIONSHIPS, NOT COMPONENTS

Many failures exist between things.

A writer can be working correctly. A reader can be working correctly. And they can still fail to communicate.

Workbench analyses the relationships between DDS entities — exposing discovery problems, incompatible QoS, type conflicts and unexpected topology — and brings them into the system model rather than leaving engineers to correlate four tools in their head.

CAPTURE AND REPLAY

A problem seen in the field becomes
a repeatable engineering scenario.

Workbench captures distributed activity for later analysis, so behaviour can be investigated after the original system is gone. Captured data can be republished into development and simulation environments at its original timing — or accelerated and slowed to support deeper investigation.

Capture it. Understand it. Replay it. Test against it.
ONE WORKBENCH, MANY IMPLEMENTATIONS

Built around the standards,
not around one vendor.

Workbench is built on DDS and RTPS rather than the assumptions of a single implementation — so it is useful in heterogeneous environments, and helps engineers understand the system they actually built rather than the portion visible through one vendor’s tooling.

Analyses

  • Nexus
  • Third-party DDS implementations
  • Mixed-vendor systems
  • Any standards-compliant DDS/RTPS

See the system. Understand the behaviour.
Find the problem.