-
Notifications
You must be signed in to change notification settings - Fork 308
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
Agent allow for configurable log directory #4497
Comments
Possibly adjusting the The cluttered files may be somewhat not an issue as the |
The Agent logs are currently stored within the application directory. As these logs roll over after 2MB, they can clutter this directory. It has been requested to allow for the log (current and archived) to go to a specific location on the host. This destination could be another folder inside the application directory (which is not removed if the Agent is removed), a different absolute directory on the same host environment or a network share (using a Windows mapped drive). This should be either supportable during the installer process (maybe as a selective checkbox that launches a screen after clicking Next?), allowing to select a location or configurable post-installation via the agent.properties. Not selecting a different location (or even showing that screen?) should use the default application installation directory for the logs.
Any upgrade to a current Agent installation, should only allow for a change to the agent.config and not prompt for a different destination.
The text was updated successfully, but these errors were encountered: