- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with metricbeat
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
The metricbeat module installs, configures and manages the Elastic metricbeat service for shipping metrics to Logstash, Kafka or Elasticsearch.
This modules currently does not manage the package repository for the elastic. The main reason for this is that the module is primarily written for enterprise environments, without an direct access to the public internet. Furthermore, as you also might want to install Logstash, Elasticsearch and Kibana in your in environment (and there is only a "all-in-one" package repository for elastic), there would be a high chance of a duplicate resource definition of the package repository.
If you don't have a central repository management in your environment (like Pulp or RedHat Satellite) prepare the package repository on your nodes with a different module (e.g. elastic_stack), or use the module parameters to switch to an "url based" installation method.
metricbeat::package_provider: 'rpm'
metricbeat::package_source: 'https://artifacts.elastic.co/packages/6.x/yum/6.4.0/metricbeat-6.4.0-x86_64.rpm'
Metricbeat requires at least one configured output. See below for example configurations.
All parameters for the metricbeat module are contained within the main metricbeat
class, so for any function of the module, set the options you want. See the common usages below for examples.
include metricbeat
Each hash entry represents a own configuration file inside of /etc/metricbeat/modules.d
.
metricbeat::modules:
'docker':
- module: docker
metricsets:
- container
- cpu
- diskio
- healthcheck
- info
- memory
- network
period: 10s
hosts: ["unix:///var/run/docker.sock"]
metricbeat::config:
output:
logstash:
hosts:
- 'logstash1.example.com:5044'
- 'logstash2.example.com:5044'
metricbeat::config:
output:
kafka:
hosts:
- 'kafka1.example.com:9092'
- 'kafka2.example.com:9092'
topic: "%{literal('%')}{[fields.kafka_topic]}"
metricbeat::config:
output:
elasticsearch:
hosts: ["localhost:9200"]
protocol: "https"
username: "elastic"
password: "changeme"
A complete example configuration using the Logstash output with authentication via the Puppet SSL certificates.
metricbeat::env:
'APPLICATION': 'puppetserver'
metricbeat::config:
name: '%{facts.fqdn}'
tags:
- '%{facts.osfamily}'
fields:
environment: '%{environment}'
application: '${APPLICATION:none}'
logging.level: 'error'
logging.selectors: ["*"]
output:
logstash:
hosts: ["logstash.example.com:5044"]
ssl.certificate_authorities: ["/etc/puppetlabs/puppet/ssl/certs/ca.pem"]
ssl.certificate: "/etc/puppetlabs/puppet/ssl/certs/%{trusted.certname}.pem"
ssl.key: "/etc/puppetlabs/puppet/ssl/private_keys/%{trusted.certname}.pem"
ssl.supported_protocols: [TLSv1.2]
ssl.cipher_suites: [ECDHE-ECDSA-AES-256-GCM-SHA384, ECDHE-RSA-AES-256-GCM-SHA384, ECDHE-ECDSA-AES-128-GCM-SHA256, ECDHE-RSA-AES-128-GCM-SHA256]
ssl.curve_types: [P-256, P-384, P-521]
ssl.renegotiation: never
metricbeat::modules:
'system':
- module: system
metricsets:
- cpu
- load
- memory
- network
- process
- process_summary
- uptime
- core
- diskio
- filesystem
- fsstat
enabled: true
period: 10s
processes: ['.*']
See REFERENCE.md
For an extensive list of supported operating systems, see metadata.json
Puppet modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. Feature requests and pull requests are appreciated.
To see who's already involved, see the list of contributors.