Skip to content

Latest commit

 

History

History
109 lines (76 loc) · 5.45 KB

README.md

File metadata and controls

109 lines (76 loc) · 5.45 KB
Raw

Grafana, Graphite & StatsD with Ansible

This playbook let you easily setup Grafana, Graphite and StatsD. You can use it to provison a dedicated server or even a virtual machine using the VagrantFile and Virtualbox

It uses Ansible as a provisionner, make sure to install Ansible before (version >= 1.6).

What gets installed with this playbook:

  • Zsh and Oh My Zsh
  • PostgreSQL
  • NginX webserver/reverse proxy
  • Python, Pip & VirtualEnv
  • NodeJS
  • Memcached
  • ElasticSearch
  • StatsD
  • Grahite with its components:
  • And finally Grafana

Setup

Before running this playbook you need to configure a few things, mostly for security purposes. All the configuration variables are defined in the playbook.yml file, I suggest you to take a look at each of them.

Global:

  • user: By default Vagrant will use the user "vagrant".

Here the most important one for Graphite:

  • graphite.secret_key: This is the django secret signin key, generate your own here
  • graphite.nginx_server_name: The domain or IP address on which you will access graphite
  • graphite.nginx_htpasswd: The .htaccess content, you can generate one from here (by default the login/pass is admin/admin).
  • graphite.nginx_enable_ssl: Wherever or not you want to use SSL, I strongly advise you to do so if you don't your credential will be sent in clear mode
  • graphite.nginx_ssl_cert: If you enable the SSL you need an SSL certificate (.crt or .pem), use the name of it here and add it inside the /files/ssl directory
  • nginx_ssl_key: If you enable the SSL you need an SSL certificate (.key), use the name of it here and add it inside the /ssl directroy

Here the most important one for Grafana:

  • grafana_version: The version of Grafana to use, check for the latest one
  • grafana_nginx_server_name: The domain or IP address on which you will access grafana
  • grafana_nginx_htpasswd: The .htaccess content, you can generate one from here (by default the login/pass is admin/admin).
  • grafana_nginx_enable_ssl: Wherever or not you want to use SSL, I strongly advise you to do so if you don't your credential will be sent in clear mode
  • grafana_nginx_ssl_cert: If you enable the SSL you need an SSL certificate (.crt or .pem), use the name of it here and add it inside the /files/ssl directory
  • grafana_nginx_ssl_key: If you enable the SSL you need an SSL certificate (.key), use the name of it here and add it inside the /ssl directroy

In order to restrict who can send data to StatsD the only way to do it is by using a Firewall and restrict the access to StatsD port 8125. You will find at the end of the playbook.yml two commented lines in order for you to do so using the UFW Firewall (I recommend to disable all access to port 8125 except for IPs you trust).

After that you will be able to access:

  • StatsD: http://your_box_ip_or_domain:8125 (Using UDP)
  • Graphite: http://graphite.nginx_server_name:8082
  • Grafana: http://grafana_nginx_server_name

Running it with Vagrant

If you want to install Grafana/Graphite on a VM using Vagrant, you need to install Vagrant and VirtualBox first.

Then hit:

$ vagrant up

Deploying with Ansible

Before running Ansible you have to add the IP address of your target server into the ansible_hosts file.

$ vi ansible_hosts

You also need to change the remote_user variable in playbook.yml to the actual user you will use to login into your target server:

$ ansible-playbook -v -i ansible_hosts playbook.yml -e target=X.X.X.X

Also if you are deploying to Ubuntu, since you won't be able to login as root, you need to pass the --sudo -K option:

$ ansible-playbook -v -i ansible_hosts playbook.yml -e target=X.X.X.X --sudo -K

(You should be able to use "target" instead of X.X.X.X in the command line but right now it's not working)

Generating a self-signed SSL Certificate

If you don't own a valid SSL certificate you can still generate a self-signed on:

$ cd files/ssl ; openssl req -x509 -newkey rsa:2048 -keyout ssl_certif.pem -out ssl_certif.pem -days 365 -nodes

Misc

Different OSes

By default, the Vagrant box runs Ubuntu 12.04, but the playbook supports Debian 7 and CentOS 6.4 as well! To try those out, uncomment the appropriate lines in the Vagrantfile and comment out the Debian lines.

Known issues

  • On CentOS, the firewall is completely closed by default (at least on the box I tried it with). So you have to manually open the relevant port (80) using iptables, or if you're not concerned about security (because you're running it locally through Vagrant), you can always flush the firewall with iptables -F.

Thanks

This project is originally based on two playbook: