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 #12577 to 7.0: Add warning for logging configuration on systemd #12662

Merged
merged 1 commit into from
Jun 25, 2019

Conversation

jsoriano
Copy link
Member

Cherry-pick of PR #12577 to 7.0 branch. Original message:

Since 7.0 we add the -e flag to all beats from the systemd unit file.
This make them to log to stderr on systems with systemd, what is the
recommended behaviour on these systems, so local logs are managed by
journald. This creates some confusion as the added flag makes beats
ignore other output settings added to the configuration files.
Add a new warning in the logging configuration page about this.

Related to #8942 and #12024

Since 7.0 we add the `-e` flag to all beats from the systemd unit file.
This make them to log to stderr on systems with systemd, what is the
recommended behaviour on these systems, so local logs are managed by
journald. This creates some confusion as the added flags make beats
ignore other output settings added to the configuration files.
Add a new warning in the logging configuration page about this.

(cherry picked from commit a6cd5e8)
@jsoriano jsoriano merged commit 8620da8 into elastic:7.0 Jun 25, 2019
@jsoriano jsoriano deleted the backport_12577_7.0 branch June 25, 2019 19:33
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…stic#12662)

Since 7.0 we add the `-e` flag to all beats from the systemd unit file.
This make them to log to stderr on systems with systemd, what is the
recommended behaviour on these systems, so local logs are managed by
journald. This creates some confusion as the added flags make beats
ignore other output settings added to the configuration files.
Add a new warning in the logging configuration page about this.

(cherry picked from commit d8b19dc)
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