11.2 Node Status Topic [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 11.2 Node Status Topic ======

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

[[fxdemo:05-part:11-control-plane-topics:start | Return to Control Plane Topics ]]

The [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] Status Topic carries operational status messages from Phase 0 Nodes. Each Node should publish status messages at defined [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|Lifecycle]] transitions and at any additional status points required by the Node profile.

The recommended topic name is:

<code>
Control.Node.Status
</code>

A Node Status message should identify:

  - Node Identity.
  - Node Role.
  - Runtime instance identifier, where needed.
  - Current Lifecycle state.
  - Timestamp.
  - Status reason or message.
  - Build or version identifier, where available.
  - Health or readiness details, where applicable.
  - Error information, where applicable.

Each Node should publish status when it enters important Lifecycle states such as ''Starting'', ''Running'', ''Degraded'', ''Recovering'', ''Stopping'', ''Stopped'', or ''Failed''. A Node should not normally publish ''Unknown'' about itself. Observers may use ''Unknown'' when they cannot determine the current state of a Node.

The Node Status Topic should support review and acceptance Evidence. A tester or reviewer should be able to inspect status messages and confirm that each required Node started, reached its expected runtime state, and stopped or failed in a controlled, observable way.

----

<WRAP centeralign>

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

</WRAP>