====== 8.11 FX Health and Observability Node Mapping ======

[[fxdemo:04-part:08-mapping-from-fx-logical-nodes-to-implementation-artifacts:start | Go To Mapping from FX Logical Nodes to Implementation Artifacts ]]

The FX Health and Observability [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Node]] maps to the Phase 0 implementation artifact that observes and reports the implementation Node condition.

The implementation artifact performs or supports the Health Reporting [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Role]]. It receives or collects implementation representations of FX Node Status, observes lifecycle-state reports, records warnings or degraded conditions, and supports Control Plane or audit/provenance interaction when Phase 0 requires those relationships.

<WRAP table-caption>
**Table 8-9:** FX Health and Observability Node implementation mapping.
</WRAP>

^ Mapping Concern ^ Phase 0 Implementation Treatment ^
| FX logical Node | FX Health and Observability Node |
| Primary Node Role | Health Reporting Role |
| Primary Runtime Plane | FX Logical Health and Observability Plane |
| Supporting Runtime Planes | FX Logical Control Plane; FX Logical Audit and Provenance Plane |
| Primary implementation responsibility | Observe and report the implementation Node condition. |
| Primary DDS interactions | Subscribe to or publish through the DDS Topic that realizes the FX Node Status Endpoint. |
| Primary data artifact | [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] and a generated type representing FX Node Status. |
| Supporting artifacts | Health helper module, logging helper, lifecycle-state conventions, and traceability metadata. |
| Traceability expectation | Implementation artifact traces to the FX Health and Observability Node, Health Reporting Role, FX Node Status Endpoint, and FX Node Status. |

----

<WRAP centeralign>

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

</WRAP>