3f6da9781b
This adds the systemd_exporter_tls_server_config variable, equivalent to the one in node_exporter and others, enabling the use of TLS for the systemd exporter. Signed-off-by: Håvard Pettersson <haavard.pettersson@gmail.com> |
||
|---|---|---|
| .. | ||
| defaults | ||
| handlers | ||
| meta | ||
| molecule | ||
| tasks | ||
| templates | ||
| vars | ||
| README.md | ||
Ansible Role: systemd exporter
Description
Deploy prometheus systemd exporter using ansible.
Requirements
- Ansible >= 2.9 (It might work on previous versions, but we cannot guarantee it)
- gnu-tar on Mac deployer host (
brew install gnu-tar)
Role Variables
All variables which can be overridden are stored in defaults/main.yml file as well as in meta/argument_specs.yml. Please refer to the collection docs for description and default values of the variables.
Example
Playbook
Use it in a playbook as follows:
- hosts: all
roles:
- prometheus.prometheus.systemd_exporter
TLS config
See node_exporter README for more extensive example:
systemd_exporter_tls_server_config:
cert_file: /etc/systemd_exporter/tls.cert
key_file: /etc/systemd_exporter/tls.key
Local Testing
The preferred way of locally testing the role is to use Docker and molecule (v3.x). You will have to install Docker on your system. See "Get started" for a Docker package suitable to for your system. Running your tests is as simple as executing molecule test.
Continuous Intergation
Combining molecule and circle CI allows us to test how new PRs will behave when used with multiple ansible versions and multiple operating systems. This also allows use to create test scenarios for different role configurations. As a result we have a quite large test matrix which can take more time than local testing, so please be patient.
Contributing
Troubleshooting
See troubleshooting.
License
This project is licensed under MIT License. See LICENSE for more details.