====== 15.6 Container Logs ======

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

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

Containers should expose logs in a way that supports runtime inspection, troubleshooting, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] collection. The team should not depend on transient container output that disappears before reviewers can inspect it.

Container logs should identify:

  - Container name.
  - Image name and tag, where useful.
  - [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] or service Identity.
  - Startup command.
  - Configuration profile.
  - Node Lifecycle events.
  - [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] discovery or communication issues, where relevant.
  - Warnings and errors.
  - Shutdown result.

The team may capture container logs via container runtime commands, mounted log directories, standard output and standard error, or evidence-export scripts. The container documentation should identify the expected mechanism.

If a container runs a single Node, the container logs and the Node logs may overlap. The team should still preserve the distinction between the container as a packaging/runtime unit and the Node as an architectural runtime participant.

----

<WRAP centeralign>

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

</WRAP>