Add file names to list of LS config files #9321
Closed
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
karenzone
changed the title
karenzone
changed the title
karenzone
force-pushed
the
ls#8563-pipelines
branch
from
b5ad2a7
to
daac0ea
Compare
Add anchor to log4j2 topic heading for linking
karenzone
force-pushed
the
ls#8563-pipelines
branch
from
daac0ea
to
b43d14e
Compare
dedemorton
reviewed
Apr 6, 2018
| Starting with 5.0, you can configure logging for a particular subsystem in Logstash. For example, if you are | ||
| debugging issues with Elasticsearch Output, you can increase log levels just for that component. This way | ||
| When debugging problems, particularly problems with plugins, it can be helpful to increase the logging level to `DEBUG` | ||
| to get more verbose messages. Previously, you could only set a log level that applied to the entire Logstash product. |
There was a problem hiding this comment.
Now that we're 3 minors into the 6.x release, I wonder if it's still relevant to mention that this feature was added in 5.0? It might still be helpful for support to have this info, but it also makes the content seem a bit dated. Might be worth initiating a conversation on the techpubs channel.
There was a problem hiding this comment.
Excellent point and good discussion in techpubs channel. I added "Decide on best approach for version references in docs. Clean up accordingly." to my LS documentation meta issue so I won't forget it.
|
I did some crazy stuff with word wrap and squashing commits. Think I cleaned all that up.
|
andrewvc
reviewed
Apr 6, 2018
| *`jvm.options`*:: | ||
| Contains JVM configuration flags. Specify each flag on a separate line. You can also use this file to set the locale | ||
| for Logstash. | ||
| Contains JVM configuration flags. Use this file to set initial and maximum values for |
There was a problem hiding this comment.
Thanks so much for adding this!
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 9, 2018
…nchor to log4j2 topic heading for linking Fixes #9321
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 9, 2018
…nchor to log4j2 topic heading for linking Fixes #9321
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 9, 2018
…nchor to log4j2 topic heading for linking Fixes #9321
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.
Added
pipelines.ymlandlog4j2.propertiesto list of Logstash config files:https://www.elastic.co/guide/en/logstash/master/config-setting-files.html
Summary of changes: