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

Improve link to content about setting up config management

Browse source 
Fixes #8209
This commit is contained in:
DeDe Morton 2017-09-11 14:11:28 -07:00
parent bb06af1989
commit d20d837cdd
1 changed files with 17 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

33
docs/static/config-management.asciidoc vendored
View file

@ -11,18 +11,18 @@ https://forge.puppet.com/elastic/logstash[Logstash Puppet module documentation].
[role="xpack"] [role="xpack"]
[[logstash-centralized-pipeline-management]] [[logstash-centralized-pipeline-management]]
=== Centralized Pipeline Management === Centralized Pipeline Configuration Management
NOTE: Centralized pipeline management is an {xpack} feature that requires a NOTE: Centralized pipeline configuration management is an {xpack} feature that
paid {xpack} license. See the requires a paid {xpack} license. See the
https://www.elastic.co/subscriptions[Elastic Subscriptions] page for https://www.elastic.co/subscriptions[Elastic Subscriptions] page for information
information about obtaining a license. about obtaining a license.
The pipeline management feature in {xpack} centralizes the creation and The pipeline configuration management feature in {xpack} centralizes the
management of Logstash configuration pipelines. From within the pipeline creation and management of Logstash configuration pipelines. From within the
management UI, you can control multiple Logstash instances. You can add, edit, pipeline management UI, you can control multiple Logstash instances. You can
and delete pipeline configurations. On the Logstash side, you simply need add, edit, and delete pipeline configurations. On the Logstash side, you simply
to register Logstash to use the centrally managed pipeline configurations. need to register Logstash to use the centrally managed pipeline configurations.
The pipeline configurations, along with some metadata, are stored in The pipeline configurations, along with some metadata, are stored in
Elasticsearch. Any changes that you make to a pipeline definition in the UI are Elasticsearch. Any changes that you make to a pipeline definition in the UI are
@ -31,14 +31,15 @@ the pipeline. The changes are applied immediately; you do not have to restart
Logstash to pick up the changes, as long as Logtash is already registered to Logstash to pick up the changes, as long as Logtash is already registered to
use the pipeline. use the pipeline.
To use centralized pipeline management, you must install {xpack} and specify To use centralized pipeline configuration management, you must install {xpack}
the configuration management settings described in and specify the
{logstash-ref}/setup-xpack.html[Setting up {xpack}]. {logstash-ref}/settings-xpack.html#configuration-management-settings[configuration management settings]
described under {logstash-ref}/setup-xpack.html[Setting up {xpack}].
IMPORTANT: After you've configured Logstash to use centralized pipeline IMPORTANT: After you've configured Logstash to use centralized pipeline
management, you can no longer specify local pipeline configurations. This configuration management, you can no longer specify local pipeline
means that the `pipelines.yml` file and settings like `path.config` and configurations. This means that the `pipelines.yml` file and settings like
`config.string` are inactive when this feature is enabled. `path.config` and `config.string` are inactive when this feature is enabled.
==== Pipeline management UI ==== Pipeline management UI