Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the same location for messages.log regardless of tracing enabled or not #677

Open
leochr opened this issue Jan 30, 2025 · 0 comments
Open

Comments

@leochr
Copy link
Member

leochr commented Jan 30, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant