github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 06:37:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Clarify how cli options affect settings file

Browse source 
Fixes #6784
This commit is contained in:
DeDe Morton 2017-03-02 16:10:08 -08:00
parent bc668ee5b5
commit 330f30665f
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/static/running-logstash-command-line.asciidoc vendored
View file

@ -21,6 +21,10 @@ the `mypipeline.conf` file:
bin/logstash -f mypipeline.conf
----
Any flags that you set at the command line override the corresponding settings
in the Logstash <<logstash-settings-file,settings file>>, but the settings file
itself is not changed. It remains as-is for subsequent Logstash runs.
Specifying command line options is useful when you are testing Logstash.
However, in a production environment, we recommend that you use the Logstash
<<logstash-settings-file,settings file>> to control Logstash execution. Using
@ -28,9 +32,6 @@ the settings file makes it easier for you to specify multiple options, and it
provides you with a single, versionable file that you can use to start up
Logstash consistently for each run.
Any flags that you set at the command line override the corresponding settings
in the Logstash <<logstash-settings-file,settings file>>.
[[command-line-flags]]
==== Command-Line Flags