- Metricbeat Reference: other versions:
- Overview
- Getting started with Metricbeat
- Setting up and running Metricbeat
- Upgrading Metricbeat
- How Metricbeat works
- Configuring Metricbeat
- Specify which modules to run
- Specify general settings
- Load external configuration files
- Configure the internal queue
- Configure the output
- Set up index lifecycle management
- Specify SSL settings
- Filter and enhance the exported data
- Parse data by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- Autodiscover
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- metricbeat.reference.yml
- Beats central management
- Modules
- Aerospike module
- Apache module
- Ceph module
- Couchbase module
- Docker module
- Dropwizard module
- Elasticsearch module
- Elasticsearch ccr metricset
- Elasticsearch cluster_stats metricset
- Elasticsearch index metricset
- Elasticsearch index_recovery metricset
- Elasticsearch index_summary metricset
- Elasticsearch ml_job metricset
- elasticsearch ml_job MetricSet
- Elasticsearch node metricset
- Elasticsearch node_stats metricset
- Elasticsearch pending_tasks metricset
- elasticsearch pending_tasks MetricSet
- Elasticsearch shard metricset
- envoyproxy module
- Etcd module
- Golang module
- Graphite module
- HAProxy module
- HTTP module
- Jolokia module
- Kafka module
- Kibana module
- Kubernetes module
- Kubernetes apiserver metricset
- Kubernetes container metricset
- Kubernetes event metricset
- Kubernetes node metricset
- Kubernetes pod metricset
- Kubernetes state_container metricset
- Kubernetes state_deployment metricset
- Kubernetes state_node metricset
- Kubernetes state_pod metricset
- Kubernetes state_replicaset metricset
- Kubernetes state_statefulset metricset
- Kubernetes system metricset
- Kubernetes volume metricset
- kvm module
- Logstash module
- Memcached module
- MongoDB module
- Munin module
- MySQL module
- Nginx module
- PHP_FPM module
- PostgreSQL module
- Prometheus module
- RabbitMQ module
- Redis module
- System module
- System core metricset
- System cpu metricset
- System diskio metricset
- System filesystem metricset
- System fsstat metricset
- System load metricset
- System memory metricset
- System network metricset
- System process metricset
- System process_summary metricset
- System raid metricset
- System socket metricset
- System socket_summary metricset
- System uptime metricset
- traefik module
- uwsgi module
- vSphere module
- Windows module
- ZooKeeper module
- Exported fields
- Aerospike fields
- Alias fields
- Apache fields
- Beat fields
- Ceph fields
- Cloud provider metadata fields
- Common fields
- Couchbase fields
- Docker fields
- Docker fields
- Dropwizard fields
- Elasticsearch fields
- envoyproxy fields
- Etcd fields
- Golang fields
- Graphite fields
- HAProxy fields
- Host fields
- HTTP fields
- Jolokia fields
- Kafka fields
- Kibana fields
- Kubernetes fields
- Kubernetes fields
- kvm fields
- Logstash fields
- Memcached fields
- MongoDB fields
- Munin fields
- MySQL fields
- Nginx fields
- PHP_FPM fields
- PostgreSQL fields
- Prometheus fields
- RabbitMQ fields
- Redis fields
- System fields
- traefik fields
- uwsgi fields
- vSphere fields
- Windows fields
- ZooKeeper fields
- Monitoring Metricbeat
- Securing Metricbeat
- Troubleshooting
- Contributing to Beats
Enroll Beats in central management
editEnroll Beats in central management
editThis functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
You need to enroll Beats to register them in central management and establish trust. Enrolled Beats will have the credentials needed to retrieve configurations from Kibana.
During the enrollment process:
- The Beat contacts Kibana and tries to register
- Kibana registers the Beat instance and returns an access token for configuration polling
- The enroll command creates a backup of your configuration and then overwrites the current settings so they can be managed centrally
To enroll Beats, use either token-based or username and password-based enrollment.
Prerequisites
edit-
Verify that your Elastic license includes the Beats central management feature.
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.
- Enable security in Kibana to ensure that only users with sufficient privileges are able to access Beats configurations.
-
Assign the
beats_admin
role to any users who need to enroll Beats or manage configuration settings in central management. - If you plan to use the sample Kibana dashboards provided with Metricbeat, load the dashboards before enrolling the Beat.
Token-based enrollment
editToken-based enrollment is recommended if you are enrolling Beats manually.
To use token-based enrollment, go to Kibana → Management → Beats and click
Enroll Beat
. Select the Beat type and operating system, then copy and run the
command for enrolling the Beat.
The command has this format:
metricbeat enroll KIBANA_URL TOKEN
-
KIBANA_URL
- The URL of the Kibana instance you will use for central management.
-
TOKEN
- The enrollment token generated by the Central Management UI. The enrollment token will expire as soon as it’s used.
For example:
metricbeat enroll http://xyz.gov:5601 70f4b584e8024b96b682c46125a8d81
Repeat this process to enroll additional Beats.
Windows users: If you installed Metricbeat as a service, you must also set
-path.data
to "C:\ProgramData\metricbeat"
when you
run the enroll command. For example:
.\metricbeat.exe enroll http://xyz.gov:5601 70f4b584e8024b96b682c46125a8d81a
-path.data "C:\ProgramData\metricbeat"
Why? The service installation script, install-service-metricbeat.ps1
,
changes the default data path to match the convention used for Windows. If you
run the enroll command without specifying the correct data path, Metricbeat
will be enrolled in central management with the wrong UUID and unable to receive
the configuration.
Username and password-based enrollment
editYou can also enroll by specifying a username and password. This is the recommended way for scripted deploys:
metricbeat enroll KIBANA_URL --username USER --password METHOD [--force]
-
--username USER
-
The username to use for password-based enrollment. The default
username is
elastic
. -
--password METHOD
-
The method to use for getting the password. Available options are:
-
env:VAR_NAME
gets the password from the environment variableVAR_NAME
-
stdin
prompts the user for a password. This is the default.
-
-
--force
- Overwrites the current settings without asking for confirmation.
For example:
metricbeat enroll http://xyz.gov:5601 --username myuser --password stdin
Windows users: If you installed Metricbeat as a service, you must also set
-path.data
to "C:\ProgramData\metricbeat"
when you
run the enroll command. For example:
.\metricbeat.exe enroll http://xyz.gov:5601 --username myuser --password stdin
-path.data "C:\ProgramData\metricbeat"
Why? The service installation script, install-service-metricbeat.ps1
,
changes the default data path to match the convention used for Windows. If you
run the enroll command without specifying the correct data path, Metricbeat
will be enrolled in central management with the wrong UUID and unable to receive
the configuration.
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now