2018-11-30 19:25:06 +01:00
|
|
|
|
[[managing-beats]]
|
2018-12-06 21:50:44 +01:00
|
|
|
|
[role="xpack"]
|
2020-02-06 18:16:32 +01:00
|
|
|
|
== {beats} Central Management
|
2018-11-30 19:25:06 +01:00
|
|
|
|
|
2019-11-18 20:17:40 +01:00
|
|
|
|
include::{asciidoc-dir}/../../shared/discontinued.asciidoc[tag=cm-discontinued]
|
2018-12-06 21:50:44 +01:00
|
|
|
|
|
2020-06-12 16:39:36 +02:00
|
|
|
|
To use the Central Management UI, open the menu, go to *Stack Management > {beats} > Central Management*, then define and
|
2018-11-30 19:25:06 +01:00
|
|
|
|
manage configurations in a central location in {kib} and quickly deploy
|
|
|
|
|
configuration changes to all {beats} running across your enterprise. For more
|
|
|
|
|
about central management, see the related {beats} documentation:
|
|
|
|
|
|
|
|
|
|
* {filebeat-ref}/configuration-central-management.html[{filebeat} documentation]
|
|
|
|
|
* {metricbeat-ref}/configuration-central-management.html[{metricbeat} documentation]
|
|
|
|
|
|
|
|
|
|
[NOTE]
|
|
|
|
|
====
|
|
|
|
|
This feature requires an Elastic license that includes {beats} central
|
|
|
|
|
management.
|
|
|
|
|
|
2020-06-12 16:39:36 +02:00
|
|
|
|
Don't have a license? You can start a 30-day trial. Open the menu, go to
|
|
|
|
|
*Stack Management > Elasticsearch > License Management*. At the end of the trial
|
2018-11-30 19:25:06 +01:00
|
|
|
|
period, you can purchase a subscription to keep using central management. For
|
|
|
|
|
more information, see https://www.elastic.co/subscriptions and
|
|
|
|
|
{stack-ov}/license-management.html[License Management].
|
|
|
|
|
====
|
|
|
|
|
|
|
|
|
|
{kib} makes it easy for you to use central management by walking you through the
|
|
|
|
|
enrollment and configuration process step by step the first time you use the
|
|
|
|
|
Central Management UI.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[float]
|
|
|
|
|
=== Enroll {beats}
|
|
|
|
|
|
|
|
|
|
You need to enroll {beats} to register them in central management and establish
|
|
|
|
|
trust. Enrolled {beats} will have the credentials needed to retrieve
|
2020-02-06 18:16:32 +01:00
|
|
|
|
configurations from {kib}.
|
2018-11-30 19:25:06 +01:00
|
|
|
|
|
|
|
|
|
[float]
|
|
|
|
|
=== Create configuration tags
|
|
|
|
|
|
|
|
|
|
A _configuration tag_ is a group of configuration blocks that you can apply to
|
|
|
|
|
one or more {beats}. For example, you can create a tag called `development` to
|
2020-02-06 18:16:32 +01:00
|
|
|
|
group configurations for {beats} running in your development environment.
|
2018-11-30 19:25:06 +01:00
|
|
|
|
|
|
|
|
|
The first time you walk through the enrollment process, you'll create a
|
|
|
|
|
configuration tag that's applied to the {beats} instance you're enrolling.
|
|
|
|
|
|
|
|
|
|
After that, under *Configuration tags*, you can create additional tags and
|
|
|
|
|
apply them to any enrolled {beats}, and the {beats} will use the configurations
|
|
|
|
|
defined in the tag.
|
|
|
|
|
|
|
|
|
|
[float]
|
|
|
|
|
=== Add configuration blocks
|
|
|
|
|
|
|
|
|
|
Add one or more configuration blocks to the tag. A tag can have configuration
|
|
|
|
|
blocks for different types of {beats}. When the enrolled {beats} run, they will
|
|
|
|
|
use the configuration blocks that are valid for their type.
|
|
|
|
|
|
2019-02-01 02:03:09 +01:00
|
|
|
|
Central management supports configuration settings for:
|
|
|
|
|
|
|
|
|
|
* {filebeat} modules
|
|
|
|
|
* {metricbeat} modules
|
|
|
|
|
* {filebeat} inputs
|
2020-02-06 18:16:32 +01:00
|
|
|
|
* {filebeat} and {metricbeat} outputs
|
2019-02-01 02:03:09 +01:00
|
|
|
|
|
|
|
|
|
NOTE: Central management supports the following outputs only: {es}, {ls}, Kafka,
|
|
|
|
|
and Redis. Other output types are not supported for {beats} that are enrolled in
|
|
|
|
|
central management.
|
|
|
|
|
|
|
|
|
|
Use the Central Management UI to define and manage settings for supported
|
|
|
|
|
configuration blocks. You cannot define those settings in local {beats}
|
|
|
|
|
configuration files. For configuration blocks that are not supported by central
|
|
|
|
|
management, configure the settings in the local configuration file after
|
2020-02-06 18:16:32 +01:00
|
|
|
|
enrolling the Beat in central management.
|
2019-02-01 02:03:09 +01:00
|
|
|
|
|
2018-11-30 19:25:06 +01:00
|
|
|
|
[float]
|
|
|
|
|
=== Manage enrolled {beats}
|
|
|
|
|
|
|
|
|
|
Under *Enrolled {beats}*, you can view the list of enrolled {beats} to see
|
|
|
|
|
details, including the type, applied tags, configuration status, and the last
|
|
|
|
|
configuration update. Click the *Beat name* or *Type* column heading to sort the
|
|
|
|
|
list. To filter the list, enter a search string. If there are errors in a
|
|
|
|
|
configuration, you’ll see an Error status in the Central Management UI and need
|
|
|
|
|
to look at {beats} logs to troubleshoot the problem.
|
|
|
|
|
|
|
|
|
|
You can add or remove tags, and the configuration changes are automatically
|
|
|
|
|
deployed to all {beats} that have the tag. Avoid applying tags with conflicting
|
|
|
|
|
configurations. Because the configurations for all assigned tags are merged,
|
|
|
|
|
conflicting configurations result in errors.
|
|
|
|
|
|
|
|
|
|
You can unenroll {beats} to remove them from central management.
|
|
|
|
|
|
|
|
|
|
[float]
|
|
|
|
|
=== Manage tags
|
|
|
|
|
|
|
|
|
|
Under *Configuration tags*, you can select tags and delete them, or you can
|
|
|
|
|
drill down into a tag to add, modify, or remove configuration blocks from the
|
|
|
|
|
tag. When you change the configuration blocks or remove tags, the configuration
|
|
|
|
|
changes are automatically deployed to all {beats} that have the tag.
|