Deploy bind_exporter using ansible.
- Ansible >= 2.7 (It might work on previous versions, but we cannot guarantee it)
All variables which can be overridden are stored in defaults/main.yml file as well as in table below.
| Name | Default Value | Description |
|---|---|---|
| `bind_exporter_version | "0.4.0" | Version of the bind_exporter. Also accepts latest as a parameter. |
bind_exporter_binary_local_dir: |
"" | Allows to use local packages instead of ones distributed on github. As parameter it takes a directory where bind_exporter binary is stored on host on which ansible is ran. This overrides bind_exporter_version parameter |
bind_exporter_web_listen_address |
"0.0.0.0:9119" | Address on which bind_exporter will listen. |
bind_exporter_pid_file: |
"/run/named/named.pid" | The PID file of the bind process. |
bind_exporter_stats_groups |
"server,view" | A list of stats groups to poll. |
bind_exporter_stats_url |
"http://localhost:8053/" | The URL of the bind statistics-channel. |
bind_exporter_stats_version |
"auto" | Which polling API to use. |
Use it in a playbook as follows:
- hosts: all
roles:
- cloudalchemy.bind_exporterWe provide demo site for full monitoring solution based on prometheus and grafana. Repository with code and links to running instances is available on github and site is hosted on DigitalOcean.
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.
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.
See troubleshooting.
This project is licensed under MIT License. See LICENSE for more details.