141b38a083
The built-in 'remote_monitoring_user' has full permissions on monitoring indices, which is more than Metricbeat needs to collect metrics from remote components. |
||
|---|---|---|
| .. | ||
| config | ||
| .dockerignore | ||
| Dockerfile | ||
| README.md | ||
| metricbeat-compose.yml | ||
README.md
Metricbeat
Metricbeat is a lightweight shipper that you can install on your servers to periodically collect metrics from the operating system and from services running on the server. Metricbeat takes the metrics and statistics that it collects and ships them to the output that you specify, such as Elasticsearch or Logstash.
Usage
This extension requires the beats_system and monitoring_internal users to be created and initialized with a
password. In case you haven't done that during the initial startup of the stack, please refer to How to re-execute
the setup to run the setup container again and initialize these users.
To include Metricbeat in the stack, run Docker Compose from the root of the repository with an additional command line
argument referencing the metricbeat-compose.yml file:
$ docker-compose -f docker-compose.yml -f extensions/metricbeat/metricbeat-compose.yml up
Configuring Metricbeat
The Metricbeat configuration is stored in config/metricbeat.yml. You can modify this file
with the help of the Configuration reference.
Any change to the Metricbeat configuration requires a restart of the Metricbeat container:
$ docker-compose -f docker-compose.yml -f extensions/metricbeat/metricbeat-compose.yml restart metricbeat
Please refer to the following documentation page for more details about how to configure Metricbeat inside a Docker container: Run Metricbeat on Docker.
See also
Screenshots
