Add warning for logging configuration on systemd #12577
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
jsoriano
added
the
needs_backport
|
I think we should add the option |
|
|
kvch
approved these changes
Jun 18, 2019
jsoriano
added
v7.2.0
and removed
needs_backport
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Jun 25, 2019
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
added a commit
to jsoriano/beats
that referenced
this pull request
Jun 25, 2019
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
added a commit
to jsoriano/beats
that referenced
this pull request
Jun 25, 2019
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
added a commit
that referenced
this pull request
Jun 25, 2019
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
added a commit
that referenced
this pull request
Jun 25, 2019
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
added a commit
that referenced
this pull request
Jun 25, 2019
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)
DStape
pushed a commit
to DStape/beats
that referenced
this pull request
Aug 20, 2019
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.
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…stic#12660) 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)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…stic#12661) 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)
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since 7.0 we add the
-eflag 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