Icinga 2 is an open source tracking system which examines the availability of your network resources, alerts users of failures and creates performance information for reporting.
Extensible and scalable, Icinga 2 can monitor big, complicated environments across multiple areas. Graphite stores performance information on a configurable duration. Via a specified user interface, services can send metrics to Graphite, which are then saved for the designated duration. Charts can be produced from the different metrics through the incorporated web interface in Graphite, took a look this link to see more.
What is Grafana
Graphite does have a personal web user interface but it is neither versatile nor appealing. This is where Grafana comes in. Grafana is a frontend for various storage metrics, supporting Graphite, InfluxDB and OpenTSDB, among others. Grafana offers an intuitive user interface through which you can produce charts to represent the metrics and a range of functions to optimise their appearance and presentation. The graphs can then be summed up in control panels; you can likewise choose to display one from a specific host just, through parameterization.
Setup of Icinga2 with Graphite
Icinga2 should be set up so that all specified metrics are exported to Graphite. The Graphite element gets this data called “Carbon”. In our sample installation Carbon operates on the exact same host as Icinga2 and uses the default port, indicating no further configuration of Icinga2 is required – it suffices to export on.
Setup of Graphite Web
Grafana utilizes the frontend of Graphite as an interface for the stored metrics of Graphite so appropriate setup of Graphite-web is essential. For efficiency factors, we operate Graphite-web as a WSGI module. A variety of configuration actions are essential:
1. We produce a user database for Graphite-web. Since we will not have many users, at this moment we use SQLite as the backend for our user data.
2. We trigger the WSGI module in Apache: a2enmod wsgi
3. For simpleness the web user interface should run in a separate virtual host and by itself port. That Apache listens to this port, we include the line
” Listen 8000″ to the file “/ etc/apache2/ports. conf”.
4. The Graphite Debian package currently offers a setup apply for Apache, which is great to use with minor adjustments.
cp/ usr/share/graphite-web/ apache2- graphite.conf/ etc/apache2/sites-available/ graphite.conf
5. We can now activate the brand-new virtual host by means of a2ensite graphite and reboot Apache:
# a2ensite graphite.
6. You ought to now have the ability to reach Graphite-web at http://YOURIP:8000/ If you can not, the Apache log files in “/ var/ log/ apache2/”.