====== 15.7 Control Plane Observation ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:15-logging-and-observability:start | Return to Logging and Observability ]]

[[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] observation should provide a network-level view of the Phase 0 Node network. It should show the status of Nodes without requiring reviewers to inspect each process manually.

The team may observe the Control Plane through:

  - A control-plane observer Node.
  - A command-line observer.
  - A test harness.
  - DDS diagnostic tooling.
  - Captured status-topic output.
  - Container logs.
  - Acceptance Evidence reports.

Control Plane observation should show:

  - Required Nodes discovered or expected.
  - Status messages received.
  - Current [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|Lifecycle]] state by Node.
  - Command messages observed, where applicable.
  - Command results or acknowledgements, where applicable.
  - Missing or stale Node status.
  - Failed, degraded, or unknown Nodes.
  - Final status at shutdown.

The observer should not create architectural meaning. It reports runtime Evidence. The Node Catalogue, Topic Catalogue, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] definitions, and architecture documents define the expected Node roles, topic semantics, and message structures.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>