Icinga 2 is used by many companies in all sizes and allows you to monitor servers, applications, network hardware, services, web pages, etc. However, there is a problem when monitoring external services – many people do not have the view from the outside. You can monitor everything from your own network, but what your customer sees and uses, is not 100% guaranteed to work in this way.
Practically, Icinga 2 has a proven way to integrate Icinga 2 satellites into its own monitoring environment with its cluster and zoning concept. If you want to monitor external services, the satellite zone must be outside of your own network. Our partner NETWAYS started an open source service which offers Icinga 2 in a fully managed or satellite way.
Icinga 2 satellite helps you to check your services from your customer’s point of view. Get insights into your service metrics by choosing different locations around the globe.
Currently available locations:
- US West
There are multiple preselected check plugins available for the most common scenarios. Monitor all kinds of different services including your self-operated Icinga 2 monitoring instance. All check plugins include performance metrics like latency, execution time and status codes.
A couple of available plugins for the Icinga 2 satellite:
Try the satellite for free
- Web service checks
- E-Mail service checks
- Availability checks
Ping, ICMP, TCP/UDP
- Icinga 2
Icinga 2’s customized protocol
Full Icinga instance with Icinga Director and Grafana
Perhaps a satellite is not enough and you consider replacing your current setup. There also is a full featured Icinga instance with web based configuration and an integrated performance metric solution.
Easy configuration of your hosts and services. We offer a set of preconfigured common checks based on our varied and long lasting expertise of monitoring projects.
- System health
- Network protocols
- Application servers
Graphed metrics help you to identify load peaks immediately. Every time Icinga 2 runs a check it also collects performance metrics. Those can be used to help you to find and understand possible bottlenecks in your infrastructure.
Metrics are saved up to 12 months. Full Icinga API support and smooth integration of the most common operating systems makes integration in a breath.
Please feel free to test both installations, the Master and the Satellite. Everything is free for 30 days!
Try the master for free
We’re happy to announce another minor release for Icinga 2. This release only addresses a single bug which can cause Icinga to crash when it’s trying to remove configuration files for objects which were deleted (such as comments and downtimes for hosts and services which don’t exist anymore).
Packages for Icinga 2.6.2 for the officially supported distributions should be available shortly.
We have just released another minor update for Icinga 2. Version 2.6.1 addresses a number of issues we identified in 2.6.0 and is also at the same time the first release after our recent migration to GitHub.
Two of the fixes in this version are for crash bugs which affect reloading Icinga and passing unusually large amounts of command arguments or environment variables to child processes. There are also some documentation changes and a few other smaller bug fixes. Unlike with previous minor releases we decided not to include any ITL changes this time.
An exhaustive list of all tickets solved in 2.6.1 can be found on GitHub. Packages for 2.6.1 should become available shortly.
There’s also a recently-released new version of Icinga Web 2 (2.4.1) which introduces fixes for a few minor problems our users have reported.
Icinga 2 v2.6
This time we’re focussing on stability and bugfixes instead of adding a ton of new features. This is not to say that there aren’t any new features at all. One notable feature is the bundled NSClient++ 0.5.0 package on Windows which itself improves stability and also offers a nice REST API for querying metrics.
Previous versions had a bug which caused DowntimeStart notifications to be sent as soon as a downtime was created – rather than when the downtime had actually started. In addition to that those notifications were also re-sent each time Icinga was restarted. In an HA setup a related bug might cause Icinga to crash in those scenarios. Debugging those issues was a lot of fun that was supported by being able to test fixes in customer environments. We’ve also fixed a crash in the HTTP server when querying the REST API for example using Dashing. There also were issues with syncing comment/downtime objects between nodes and syncing objects that were global zones.
A big change coming with this release and future versions is that we have decided to deprecate and remove the “bottom up” client configuration mode. All details for this decision can be found in this issue. From the user’s view it contains design flaws and lots of unfixed bugs. Considering the fact that the Icinga “stack” with Icinga 2, Icinga Web 2 and Icinga Director prefers to use the “top down” approach with config sync and clients with command endpoints, the “bottom up” approach does not fit into this design either.
We are aware of the fact that many of you have their setups already in production. There is a dedicated chapter inside the documentation dealing with migration tips and tricks. The removal of CLI commands such as “node list” and “node update-config” will not harm the cluster communication between the nodes at all. It just removes the possibility to import and generate configuration from the client itself. We’re planning for a grace period of 2 major releases or one year until the functionality is removed entirely. For now you can still use them including deprecation warnings but are advised to plan your migration to “top down” in 2017.
There are changes in the IDO database schema for MySQL and PostgreSQL. Icinga 2 v2.6 requires Icinga Web 2 v2.4, plan your upgrade to include both.
Updated release packages are available soon. Meanwhile make sure to read the Changelog.
Icinga Web 2 v2.4
This release adds the possibility to use the Icinga 2 API as command transport for e.g. rescheduling a check or sending a custom notification. If you are planning to put your Icinga Web 2 application on a different web server, you don’t have to fiddle with SSH tunnels opening a file handle for the external command pipe. In addition to that the Icinga 2 API is designed to send HTTP responses which enables proper error handling. No more fire and then grep the icinga2.log file anymore.
Another cool feature addition is the announce banner. If you are for example planning global maintenance tasks, this is the way to tell your users about it. We’ve also added a new command action toolbar on top of the detail view. That allows for scheduling a recheck even more quickly.
Other notable changes are a new icon in the detail view history to separate between SOFT and HARD states or a new clear button for the search field. We’ve also moved the status counts to the bottom of the screen. There also is a new package for SELinux installing proper policies for your secured server.
Updated release packages are available soon. Meanwhile make sure to read the Changelog.
Status count at the bottom
SOFT state in history detail view
Add Icinga 2 API Command Transport
Clear search field
New Action menu
Why engaging in the community matters
The feeling of being able to help others with problems that I have been stuck on in the past is amazing. I try to give back to the community as much as I take from it.
… or why you just could not stop.
Post from monitoring-portal.org
Icinga2 for the win!
Am Anfang ist es echt ne Qual und ich hab Schweiß und Tränen vergossen, bis ich alles Begriffen hatte, was ich begreifen musste, damit es bei mir so läuft wie es soll. Und auch jetzt habe ich noch 10000 Fragen die immer wieder hochkommen. ABER bisher habe ich hier, was Icinga2 angeht, immer eine gute Antwort bekommen und bin mittlerweile auch soweit, dass ich versuche, mein Wissen hier zu teilen.
Und nach all den “Qualen”, die ich am Anfang hatte, liebe ich Icinga2 umso mehr. Und es gibt so viel, was man ausprobieren, erweitern, testen kann. Ich könnte den lieben langen Tag nur Icinga2 und Icingaweb2 widmen.
Und das schönste ist, es ist schlank und performant. Die Entwicklung geht stetig vorran. Es ist jetzt schon gut und wird noch besser.
Michael Medin released NSClient++ 0.5.0 this week. We’re of course considering to update the bundled NSClient++ installer inside the Windows package.
First things first – the NSClient++ 0.5.0 Changelog mentions breaking changes, so we’ll need to test the ITL CheckCommands still working prior to the next Icinga 2 release (follow #12733). In case you want to help test yourself – you can safely upgrade the NSClient++ application in Windows yourself and fire your Icinga 2 checks against it (just install the new 0.5.0 package).
One cool thing to note about NSClient++ 0.5.0 – it comes with its own web server which also provides a REST API. That could introduce a solution for querying metrics via REST API which require rate calculation (CPU) from a running nscp service. This could be easily integrated into a native Icinga 2 client check plugin then. Let’s just try this out on my Windows 10 VM! :-)