IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Avoid YAML formatting problems How central management works »
Elastic Docs ›Metricbeat Reference [7.13]

Beats central management

edit

Beats central management

edit

Beats central management discontinued

We have ceased development on Beats central management and are working on a comprehensive solution to replace it. Thank you for participating in the beta and providing feedback. If you have any questions or concerns, please reach out to us on the Discuss forum.

When you use central management, configurations are stored centrally in Elasticsearch. To prevent an attacker from leveraging the configurations to attack your infrastructure, you must secure Elasticsearch and Kibana before using central management. See Secure a cluster.

Beats central management provides a way to define and manage configurations in a central location in Kibana and quickly deploy configuration changes to all Beats running across your enterprise.

To learn more, see How central management works.

To use central management, enroll your Beats, then use the Central Management UI in Kibana to create and apply the configurations.

This feature requires an Elastic license that includes Beats central management.

Don’t have a license? You can start a 30-day trial. At the end of the trial period, you can purchase a subscription to keep using central management. For more information, see https://www.elastic.co/subscriptions and License Management.

« Avoid YAML formatting problems How central management works »