====== 14.7 Container Logs ======

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

[[fxdemo:05-part:14-containerisation:start | Return to Containerisation ]]

Containers should expose logs in a way that supports troubleshooting, review, and acceptance [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]. Logs should not remain trapped inside transient containers that disappear when the runtime stops.

The team should define how each container produces and exposes logs. Container logs may appear through:

  - Standard output.
  - Standard error.
  - Mounted log directories.
  - Runtime log files.
  - Container runtime logging commands.
  - Evidence export scripts.

Container logs should include enough context to identify the Node or service, [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|Lifecycle]] state changes, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] source, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] participation, command handling, publication or subscription events where relevant, warnings, errors, and shutdown results.

Containers should not log secrets, credentials, private keys, tokens, or sensitive local values. If runtime Configuration includes sensitive values, the Node or container entry point should mask them in logs.

Acceptance Evidence may include container logs, Node logs, [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] status captures, script output, and test results. The team should store Evidence in the approved Evidence location rather than relying only on live terminal output.

----

<WRAP centeralign>

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

</WRAP>