{"id":240,"date":"2015-10-18T02:03:14","date_gmt":"2015-10-18T00:03:14","guid":{"rendered":"https:\/\/blog.unetresgrossebite.com\/?p=240"},"modified":"2015-12-24T17:37:18","modified_gmt":"2015-12-24T16:37:18","slug":"icinga2","status":"publish","type":"post","link":"https:\/\/blog.unetresgrossebite.com\/?p=240","title":{"rendered":"Icinga2"},"content":{"rendered":"

Before talking about\u00a0Icinga, we might need to introduce Nagios: a popular monitoring solution, released in 1999, which became a standard over the years. The core concept is pretty simple: alerting upon services failure, according to user-defined check commands, schedules, notification and escalation policies.<\/p>\n

You’ll find Nagios clients on pretty much all systems – meaning Windows. You may use SNMP to check devices or receive SNMP traps. You may use passive or active checks. You’ll probably stumble upon NRPE, Nagios Remote Plugin Executor and\/or NSCA, Nagios Service Check Acceptor.<\/p>\n

You’ve got the idea: Nagios is pretty modular. Writing plugins is relatively easy. Monitoring your infrastructure is made relatively easy, and you may automate pretty much everything using puppet classes or ansible roles.
\nStill, around 2009, two forks appeard: Icinga and Shinken, released in march and december respectively.
\nIt could be a coincidence, though it most likely was\u00a0the result of several disputes opposing Nagios Core contributors and developpers to the project maintainer, Ethan Galstad.
\nWe won’t feed that troll, you may find more data about that over here<\/a>.<\/p>\n

Anyway, in early 2009, Icinga came out. Quickly after, Shinken joined them.
\nBoth products advertised you may migrate your whole monitoring infrastructure from Nagios, just by stopping nagios daemon and starting either Shinken or Icinga one, using pretty much the same configuration.<\/p>\n

\"Icinga1.11\"<\/a>

Icinga1.11 monitoring intra.unetresgrossebite.com<\/p><\/div>\n

\"Icinga1.11\"

Icinga1.11 monitoring unetresgrossebite.com public services, as well as some of my customers services<\/p><\/div>\n

So far, so good.
\nI’ve used Shinken once, a little less than a year. I wasn’t very much satisfied –\u00a0too many workers, inducing some overhead, not really relevant for a small infrastructure like mine. It’s not really our topic. Meanwhile, I’ve been using Icinga for a couple years, I’ve installed tens of them, starting with version 1.7 to 1.9, working for Smile. All in all, I’m pretty satisfied.\u00a0I’m still running a couple Icinga monitoring my own services, it’s nice, they have a web interface that does not require you to install some SGBD (for some reason, included in\u00a0icinga-doc<\/em> package on debian).<\/p>\n

\"Icinga2\"<\/a>

Icinga2 & Icingaweb2 monitoring aws.peerio.com<\/p><\/div>\n

A while ago, Icinga released Icinga2. Sounded promising, until I realized they completely changed the way to configure their server, making my current templates and puppet classes useless.
\nArguably, Icinga2 is not a nagios server anymore. Which is not necessarily a criticism.<\/p>\n

This\u00a0week, working on AWS for Peerio<\/a>, I installed my first Icinga2 setup, writing ansible roles to automate\u00a0NRPE servers configuration, Icinga2 configuration and probes registration to my nagios servers, SMS alerts using Twilio, mail alerts using sendgrid, using http proxies everywhere – no direct internet access, on AWS private instances.
\nThere’s no public link to my gitlab, exceptionally, though I expect the repository to be opened to the public pretty soon on github.<\/p>\n

\"\"<\/a>

Icinga2 Alert Summary<\/p><\/div>\n

Point being, I’ve finally seen what Icinga2 is worth, and it’s pretty satisfying.
\nUpgrading from your former nagios server\u00a0will be relatively more complicated than migrating from Nagios to Icinga, or Nagios to Shinken. You’ll probably want to start from a fresh VM, starting from scratch.
\nIcinga2 configuration could look strange, especially after using nagios syntax for years, but it makes sense, and could drastically reduce the amount of configuration you’ll need.<\/p>\n

\"Icinga2<\/a>

Icinga2 Timeline<\/p><\/div>\n

I’m a little less convinced by their new web interface, Icingaweb2. For their defense, I had to download the code on github, the RC1 was released a few months ago<\/a>. No bug so far, maybe some CSS stuff to fix (currently, the “Add New Pane or Dashboard” button is too small, I can only read half of the text), still pretty impressive for something pulled from github with no official packaged\u00a0release.
\nI’m missing the statusmaps. The report interface looks sexier than in the previous version, though I can’t find how to generate detailed reports.<\/p>\n

Looking at their “Timeline” view, I don’t remember seeing anything like that on their previous version. Why not.<\/p>\n

The project is still young, I guess it could still be in some todolist. At least, the features represented work perfectly, their interface is pretty nice, pretty dynamic, without being some over-bloated list of tables like I was used to dealing with Shinken, Icinga or Thruk.<\/p>\n","protected":false},"excerpt":{"rendered":"

Before talking about\u00a0Icinga, we might need to introduce Nagios: a popular monitoring solution, released in 1999, which became a standard over the years. The core concept is pretty simple: alerting upon services failure, according to user-defined check commands, schedules, notification and escalation policies. You’ll find Nagios clients on pretty much all systems – meaning Windows. […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[7],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/240"}],"collection":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=240"}],"version-history":[{"count":4,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/240\/revisions"}],"predecessor-version":[{"id":250,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/240\/revisions\/250"}],"wp:attachment":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=240"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=240"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=240"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}