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 ProgramData for Windows service logs #4764

Closed
andrewkroh opened this issue Jul 26, 2017 · 1 comment
Closed

Use ProgramData for Windows service logs #4764

andrewkroh opened this issue Jul 26, 2017 · 1 comment

Comments

@andrewkroh
Copy link
Member

andrewkroh commented Jul 26, 2017

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.

I think we should move the logs to C:\ProgramData\[beatname] which is also where we store the registry files and metadata.

andrewkroh added a commit to andrewkroh/beats that referenced this issue Jul 26, 2017
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
exekias pushed a commit that referenced this issue Jul 27, 2017
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
andrewkroh added a commit to andrewkroh/beats that referenced this issue Aug 8, 2017
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 pushed a commit that referenced this issue Aug 9, 2017
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
(cherry picked from commit 47d3db4)
@tsg
Copy link
Contributor

tsg commented Sep 1, 2017

I think this can be closed.

@tsg tsg closed this as completed Sep 1, 2017
leweafan pushed a commit to leweafan/beats that referenced this issue 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

No branches or pull requests

2 participants