ansible-quickstart

Deploy Netdata with Ansible

Use this Ansible playbook to quickly deploy the Netdata Agent to one or more remote nodes and claim them to Netdata Cloud. Excellent for demo-ing Netdata's single-node and infrastructure monitoring capabilities!

This Ansible playbook does the following to every node in the hosts file.

• Install Netdata with the kickstart script.
• Claim the node to Netdata Cloud.
• Copy a simple netdata.conf configuration file into /etc/netdata on each host.

Prerequisites

• A Netdata Cloud account. Sign in and create one if you don't have one already.
• One or more nodes running a supported operating system.

This playbook has been tested on:

• Ubuntu 20.04
• CentOS 7

Quickstart

Here's how to run this playbook as quickly as possible.

First, and populate the hosts file with the IP addresses for your node(s). If you want, you can use the hostname variable to set the node's name, which appears both on the local Agent dashboard and Netdata Cloud.

203.0.113.0   hostname=node-01
203.0.113.1   hostname=node-02 

Next, edit the vars/main.yml file to change the claim_token and claim_rooms variables. To find your claim_token and claim_room, go to Netdata Cloud, then click on your Space's name in the top navigation, then click on Manage your Space. Click on the Nodes tab in the panel that appears, which displays a script with token and room strings.

Finally, run the playbook.

ansible-playbook -i hosts tasks/main.yml

When the playbook finishes, you'll see your nodes appear in Netdata Cloud!

Configuration

If you want to further configure your Netdata Agents, you can edit the existing values in vars/main.yml, or create new ones. If you create new values, you should then also edit templates/netdata.conf.j2 to add them to the configuration file that is copied to each node. See the daemon configuration doc for details about each setting.

For example, if you want to increase metrics retention, increase dbengine_multihost_disk_space and run the playbook again.

You could also create entirely new templates with this method. For example, if you want to control the health_alarm_notify.conf script with this playbook, create a new file called templates/health_alarm_notify.conf and add the settings you want to control. Add relevant variables to vars/main.yml, then create a new template task in tasks/configure.yml:

  - template:
      src: ../templates/health_alarm_notify.conf.j2
      dest: /etc/netdata/health_alarm_notify.conf
      owner: root
      group: root
      mode: u=wrx,g=rx,o=r,+x
    notify: Restart Netdata
    become: true