Consistent storage for messages logs regardless of tracing enabled or not

[leochr]

The location of the messages.log changes depending on whether Day-2 operation trace is enabled or not. By default it's written to /logs, but it changes to /serviceability/<namespace>/<pod_name> when trace operation is enabled. It's not possible to configure Liberty server to use one location for messages.log and another location for trace files. It's all controlled by logDirectory value in server.xml.

Use the same location to store messages.log. One suggestion is to symlink the default location /logs to the serviceability location at container startup via the Liberty Operator (if serviceability is enabled)

Additional discussion in this internal thread: https://ibm-cloud.slack.com/archives/C020VHDP0M8/p1738179825766089

[kabicin]

There are some container changes required to get this to work making /logs link to the serviceability directory at runtime. On operator side, the SERVICEABILITY_NAMESPACE environment variable can be set which will enable the soft link at runtime for the container.

Container changes

• Add runtime support for writing /logs to a /serviceability directory ci.docker#607
• Add runtime support for writing /logs to a /serviceability directory WASdev/ci.docker#664

Operator changes

• Link /logs output to serviceability directory #683
• Link /logs output to serviceability directory WASdev/websphere-liberty-operator#720

Test changes

• https://github.ibm.com/websphere/operators/pull/216