You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proxy logs are currently managed by Docker and they are lost when a container is destroyed and recreated. https://datastax.jira.com/browse/ZDM-338 will allow us to change the automation so that it mounts a new docker volume and uses that directory instead of the docker logs directory which we don’t control. Therefore, this ticket depends on https://datastax.jira.com/browse/ZDM-338.
Create directory and use this new directory to mount a docker volume with the log directory that is used by the proxy within the container.
Set the new parameter introduced by https://datastax.jira.com/browse/ZDM-338 and make sure that parameter is used when mounting the docker volume for the log directory.
Change playbook that retrieves logs to use the new directory managed by the proxy (and used as a docker volume) instead of the directory that is managed by docker.
┆Issue is synchronized with this Jira New Feature by Unito
┆Components: Automation
┆Priority: Major
The text was updated successfully, but these errors were encountered:
The proxy logs are currently managed by Docker and they are lost when a container is destroyed and recreated. https://datastax.jira.com/browse/ZDM-338 will allow us to change the automation so that it mounts a new docker volume and uses that directory instead of the docker logs directory which we don’t control. Therefore, this ticket depends on https://datastax.jira.com/browse/ZDM-338.
┆Issue is synchronized with this Jira New Feature by Unito
┆Components: Automation
┆Priority: Major
The text was updated successfully, but these errors were encountered: