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 a proxy managed log directory instead of docker logs #41

Open
sync-by-unito bot opened this issue Dec 1, 2022 · 0 comments
Open

Use a proxy managed log directory instead of docker logs #41

sync-by-unito bot opened this issue Dec 1, 2022 · 0 comments

Comments

@sync-by-unito
Copy link

sync-by-unito bot commented Dec 1, 2022

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

@sync-by-unito sync-by-unito bot closed this as completed Dec 21, 2022
@weideng1 weideng1 reopened this Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant