ansible-collection-prometheus/roles/chrony_exporter
gardar 94fb802ec2
removed: drop debian 10 support as it is EOL
Signed-off-by: gardar <gardar@users.noreply.github.com>
2024-09-13 14:06:13 +00:00
..
defaults patch: 🎉 automated upstream release update (#391) 2024-07-03 09:26:33 +02:00
handlers feat: Add chrony_exporter role 2023-07-23 23:18:40 +02:00
meta removed: drop debian 10 support as it is EOL 2024-09-13 14:06:13 +00:00
molecule enhancement(chrony_exporter): allows using multiple web listen addresses 2023-11-28 13:07:31 +01:00
tasks Setting one archive_path per role and setting default values 2024-02-29 10:55:40 -05:00
templates enhancement(chrony_exporter): allows using multiple web listen addresses 2023-11-28 13:07:31 +01:00
vars feat: Add chrony_exporter role 2023-07-23 23:18:40 +02:00
README.md feat: Add chrony_exporter role 2023-07-23 23:18:40 +02:00
test-requirements.txt feat: Add chrony_exporter role 2023-07-23 23:18:40 +02:00
TROUBLESHOOTING.md feat: Add chrony_exporter role 2023-07-23 23:18:40 +02:00

graph logo

Ansible Role: chrony_exporter

Description

Deploy prometheus chrony_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)
  • Passlib is required when using the basic authentication feature (pip install passlib[bcrypt])

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.chrony_exporter

TLS config

Before running chrony_exporter role, the user needs to provision their own certificate and key.

- hosts: all
  pre_tasks:
    - name: Create chrony_exporter cert dir
      file:
        path: "/etc/chrony_exporter"
        state: directory
        owner: root
        group: root

    - name: Create cert and key
      openssl_certificate:
        path: /etc/chrony_exporter/tls.cert
        csr_path: /etc/chrony_exporter/tls.csr
        privatekey_path: /etc/chrony_exporter/tls.key
        provider: selfsigned
  roles:
    - prometheus.prometheus.chrony_exporter
  vars:
    chrony_exporter_tls_server_config:
      cert_file: /etc/chrony_exporter/tls.cert
      key_file: /etc/chrony_exporter/tls.key
    chrony_exporter_basic_auth_users:
      randomuser: examplepassword

Demo site

We provide an example site that demonstrates a full monitoring solution based on prometheus and grafana. The repository with code and links to running instances is available on github and the site is hosted on DigitalOcean.

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 for your system. Running your tests is as simple as executing molecule test.

Continuous Integration

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 quite a large test matrix which can take more time than local testing, so please be patient.

Contributing

See contributor guideline.

Troubleshooting

See troubleshooting.

License

This project is licensed under MIT License. See LICENSE for more details.