How To: Set Up Active Directory Authentication for Icinga New Web

Icinga New Web was always designed with the larger organisation in mind. Often in such networks, Active Directory is used to manage the authentication and authorization of many users. So it makes sense to integrate the monitoring interface into this existing infrastructure. Luckily, it is very easy to set up Active Directory authentication in Icinga – thanks to a quick guide provided by Sebastian Waitz.
From editing the config in icinga-web/app/modules/AppKit/config/ (or auth.xml) to suit your environment, saving the changes and clearing the cache, to running a tail on the log file and testing the config, the whole process is as easy as cut and paste.
Have a look at Sebastian’s wiki guide, and get in touch with us and others users in the community on the user mailing list, IRC and the Icinga-Portal forum if you need more help. You’re also welcome to add your own ‘how-to’ and share the Icinga love!

How To: Dual Stack (IPv4 & IPv6) Monitoring with Icinga

As of v1.3, Icinga has been capable of dual stack monitoring. Making good use of Icinga Wiki, Michael Friedrich offered his tips on the very simply integration of IPv6 alongside existing IPv4 addresses.
One way is by using two different macros to assign service definitions to the host eg. $HOSTADDRESS$, $HOSTADDRESS6$ and then creating separate check commands with those. Eg. check_ping for IPv4 and IPv6.
Another, more convenient way is via the check_multi plugin by Matthias Flacke. The simple 4 step process can be found under the ‘HowTos’ category of Icinga Wiki. Simply install > define command > define host> define check commands and you should end up with:

Check out the dual stack monitoring guide yourself and feel free to browse or add your own guides to Icinga Wiki.
Cheers to Michael and Matthias for their contributions!
(Added 1/7/12) NOTE: Icinga Core is equipped with configuration attributes and command macros to enable both Icinga Classic and Icinga Web to display IPv6 as well as IPv4 addresses. Dualstack monitoring is only possible with plugins that support both types of addresses as the connection layer is located outside Icinga Core.

How To: Create Cronk Categories

The new Icinga Web is beloved for its easy to view and easy to customize Cronks. These nifty widgets can be easily customised to show exactly what the user needs, but also easily organised into neat categories.
With the release of v1.3, users could create these categories in a few simple clicks in the new Icinga Web interface:

This is convenient, but some understandably still prefer doing this on the command line. For those who prefer having their configurations in one tidy place when upgrading versions, Sebastian Waitz gave his tips for creating Cronk categories manually in Icinga Wiki.
Simply copy and paste Sebastian’s code with your relevant revisions into the file icinga-web/app/modules/Cronks/config/cronks.xml. To assign Cronks to the relevant categories, call up the desired Cronk templates in the same file, and add the line specifying your desired categories:

<ae:parameter name="categories">mycategory1,mycategory2</ae:parameter>

Check out the full guide in the ‘HowTos’ space, and feel free to browse or add your own guides to Icinga Wiki. Cheers to Sebastian for his contribution!

How to use Icinga bug report (redmine)

If you have been looking closely at the icinga front page you would have noticed a new button link on the right hand side of the site called “Report a Bug” below is what we are talking about…
As the code for Icinga is a continuous work in progress there is bound to be the occasion where you will encounter a bug! Now instead of just leaving this and assuming that the matter will just be resolved in the next release it’s best to open a bug report against what ever you find.
If you haven’t already done so, you will need to create an account, to do this you need to click on the Development drop down menu at the top of the Icinga website, then on Register for Icinga

You will then need to complete the form to create your account…

Once your account has been created you will be E-mailed an code that will enable you to the use the login …

Now that you have your account and you have logged in you will need to select the project that you wish to report against, to do this simply click on the projects link at the top of the page …

You will now have the option to select the current projects …

Now that you have selected the sub project (in this image it’s the Core) you now raise your bug by clicking on the “New Issue”

From here is where you will fill in all the details you can about the problem you have …

You can at any point click on “preview”, to review your work …

Once you are satisfied you have included all that you can to best describe the situation, then remember to click on “Create” you will then be redirected to the newly created bug report…

If you missed something don’t worry you can simply click on “Update” and add further information. remembering to click on “Submit” to add the update!