Automated Monitoring – Icinga meets Foreman

foreman logoAutomated monitoring configuration has many facilities. Some use configuration management software such as Puppet or Chef to deploy their host and service definitions. Others use the Director to import hosts from an existing CMDB and users from Active Directory. Independent from the technique that you use, I am sure we all agree that automated monitoring configuration is a huge benefit.

Today I am pleased to tell you about a new mechanism that came up recently to automate host creation in Icinga. The Foreman is a complete lifecycle management tool for physical and virtual servers. Servers can be installed classically via PXE or by using a cloud provider like Azure or DigitalOcean. You can also easily spawn Docker containers. The Foreman integrates configuration management tools such as Puppet, Chef or Ansible to set up and configure software after the installation. The list of available plugins is endless. (more…)

Vagrant box updates: Elastic Stack, InfluxDB & Icinga Web 2 modules

A while back we’ve written about changes inside our Vagrant box demo environments – and many things happened ever since.

There are a couple of new Icinga Web 2 modules directly integrated into the Vagrant boxes (Director, Grafana, Cube, Globe). In terms of metrics and event collecting we’ve integrated Elastic Stack with Icingabeat and also InfluxDB with Grafana. We are happy to release v1.3.0 today.

(more…)

Moooh!

A while back Vanessa, fellow co-worker of mine at NETWAYS, had a great idea – let’s help children in Tansania and get them a cow. Guess which name we’ve chosen – “Icinga“. In late 2015 we had the pleasure to learn that Icinga finally arrived and continues to help and explore the world.

Our baby cow Icinga has grown up and will be getting fertilised this year. Soon we will be able to welcome even more “Icinga” baby cows :-)

Happy Easter from team Icinga!

 

Process Icinga Logs with Logstash

Central log management has always been a topic for almost every sysadmin. In the past we used a central syslog server to collect all logs from clients and store them in plain text files. Instead of searching the logs on 10 web servers, the sysadmin had to run just a single grep command on one machine. When someone managed to hack into your server, he probably wasn’t fast or clever enough to disable the remote logging. He did what he did, but your logs were save for later analysis. In an ideal world even network hardware would send their logs to this central syslog instance. Well, in an ideal world the “syslog” format would be the same on each device. In an ideal world developers would use reasonable and standardised timestamp formats. Instead, we have to write regexes for the umpteenth time to parse this stuff. Sigh. (more…)

Monthly Snap March: Icinga Camp, Partners, Trainings, Icingabeat, approved Puppet module

March was all about our lovely community. We’ve had Icinga Camp Berlin and San Francisco, and also joined FLOSSUK. You’ll also recognize that our Puppet module for Icinga 2 was officially approved by Puppet. Blerim released icingabeat and blogged about it at the Elastic blog. And many more things happened …

We’ve also thought about 1st of April, but hey – we have so many great things to share and work on, we’ll skip it for 2017 ;-)

(more…)

Releasing Icingabeat

Today we are happy to announce the release of Icingabeat v1.0!icingabeat checkresults

Beats are lightweight data shippers. They are based on libbeat and written in Go. You install a Beat on your server to collect various data and forward it either to Logstash or directly to Elasticsearch. For example, there is Filebeat to read log files, Metricbeat to fetch metrics from operating systems or Packetbeat to inspect network packets. Icingabeat collects data from the Icinga API. It can open a stream to receive events and simultaneously poll the current status of Icinga 2 periodically.

(more…)