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

Cherry-pick #4765 to 6.0: Use ProgramData for Windows service logs #4847

Merged
merged 1 commit into from
Aug 9, 2017

Conversation

andrewkroh
Copy link
Member

Cherry-pick of PR #4765 to 6.0 branch. Original message:

The logs for Beats that are running as Windows services are currently written to C:\Program Files\[beatname]\logs (or the extract path which is path.home). Our Getting Started guides say that the logs go to C:\ProgramData\[beatname]\Logs. This PR sets path.log for the Windows service to C:\ProgramData\[beatname]\logs.

See #4764

The logs for Beats that are running as Windows services are currently written to `C:\Program Files\[beatname]\logs` (or the extract path which is `path.home`). Our Getting Started guides say that the logs go to `C:\ProgramData\[beatname]\Logs`. This PR sets `path.log` for the Windows service to `C:\ProgramData\[beatname]\logs`.

See elastic#4764
(cherry picked from commit 47d3db4)
@tsg tsg merged commit 695f923 into elastic:6.0 Aug 9, 2017
@andrewkroh andrewkroh deleted the backport_4765_6.0 branch October 23, 2017 20:19
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
The logs for Beats that are running as Windows services are currently written to `C:\Program Files\[beatname]\logs` (or the extract path which is `path.home`). Our Getting Started guides say that the logs go to `C:\ProgramData\[beatname]\Logs`. This PR sets `path.log` for the Windows service to `C:\ProgramData\[beatname]\logs`.

See elastic#4764
(cherry picked from commit 2169bdd)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants