mirror of
https://github.com/elastic/logstash.git
synced 2025-04-24 22:57:16 -04:00
45 lines
1.6 KiB
Text
45 lines
1.6 KiB
Text
[role="xpack"]
|
|
[[configuring-centralized-pipelines]]
|
|
=== Configuring Centralized Pipeline Management
|
|
++++
|
|
<titleabbrev>Centralized Pipeline Management</titleabbrev>
|
|
++++
|
|
|
|
To configure
|
|
{logstash-ref}/logstash-centralized-pipeline-management.html[centralized pipeline management]:
|
|
|
|
. Verify that you are using a license that includes the pipeline management
|
|
feature.
|
|
+
|
|
--
|
|
For more information, see https://www.elastic.co/subscriptions and
|
|
{kibana-ref}/managing-licenses.html[License management].
|
|
--
|
|
|
|
. Specify
|
|
<<configuration-management-settings,configuration management settings>> in the
|
|
`logstash.yml` file. At a
|
|
minimum, set:
|
|
+
|
|
* `xpack.management.enabled: true` to enable centralized configuration
|
|
management.
|
|
* `xpack.management.elasticsearch.hosts` to specify the Elasticsearch
|
|
instance that will store the Logstash pipeline configurations and metadata.
|
|
* `xpack.management.pipeline.id` to register the pipelines that you want to
|
|
centrally manage.
|
|
|
|
. Restart Logstash.
|
|
|
|
. If your Elasticsearch cluster is protected with basic authentication, assign
|
|
the built-in `logstash_admin` role as well as the `logstash_writer` role to any users who will use centralized pipeline
|
|
management. See <<ls-security>> for more information.
|
|
|
|
NOTE: Centralized management is disabled until you configure and enable
|
|
{security-features}.
|
|
|
|
IMPORTANT: After you've configured Logstash to use centralized pipeline
|
|
management, you can no longer specify local pipeline configurations. This means
|
|
that the `pipelines.yml` file and settings like `path.config` and
|
|
`config.string` are inactive when this feature is enabled.
|
|
|
|
include::{log-repo-dir}/static/settings/configuration-management-settings.asciidoc[]
|