Icinga Reporting 1.8.2 Bugfix Release

Took a little longer than expected, but thanks to all testers and reporters, we can provide another 1.8.2 release – this time for Icinga Reporting.
Please note, that this release is fully tested with the latest JasperServer 5.0.0. Furthermore, the least supported version will be JasperServer 4.5.0.

  • fix queries for host/service availability/activity report #3312 #3400
  • fix empty reports and reversed OK/NOK #3331
  • fix compatibility with jasperreports <= 4.6 #3481
  • fix host overview with empty contacts and contactgroups #3686
  • test support for jasperserver 5.0.0 #3501
  • define the least supported jasperserver version (4.5.0) #3502

Icinga Reporting 1.8.2 is available on Github. As usual, please report any bugs and/or feature requests to our development tracker, and look for help on the support channels.

Icinga Reporting 1.8 Preview

At the moment we are working heavily on the upcoming Icinga 1.8 version of Icinga Reporting. Beside a new SLA function (thanks to Thomas Gelf) we’ve redesigned all templates and integrated some stunning new reports. We’ve also added a time-range selector (last week, last month and last year) to every time-range related report. Makes scheduling and automated report distribution much much easier.
Next up, we’ve got enhanced compatibility for PostgreSQL in the works. Please check out the current git-master to test the new templates. Feedback is always welcome.
Have a nice weekend!

SLA Reporting with Added Precision

If you have upgraded to Icinga Web 1.6 you may already be familiar with the new SLA extension in IDOUtils. The optional module is our response to the old niggle from the community that data written to database could be better used. So we have taken the opportunity to add a table to the database model and fiddle with IDO2DB. The end result is ‘enable_sla’ in your IDOUtils configuration files, which takes events and identifies the periods of scheduled downtime and acknowledgment for more accurate SLA reporting.

You could say, it improves SLA results too, by making it clearer, to what extent a critical event is actually critical or being resolved 😉
Coding and coordination aside, the concept behind the SLA extension is actually quite simple. We added a SLA history table to the database model, which organizes event start and end times, object id, state and state type as well as acknowledgement and scheduled downtime. Then in IDO2DB we added extra logic to write data from the core to the aforementioned table correctly.

At the moment you can view SLA data in the Icinga Web interface’s new tackle cronk, in the form of a pie chart. This is just the beginning though. We hope to integrate SLA history into Icinga Reporting with even more refined metrics.
So perhaps in the (not too far) future, you may be able to open up Icinga Reporting and call up a diagram that shows service availability for the year, though only from Monday – Friday, 9 am – 5 pm, discounting scheduled downtimes and acknowledgement periods. That maybe something worth waiting for – or even better, contributing to.

Icinga Web 1.5.2 released

Just last week the core team released 1.5.1, and now as promised here is Icinga Web 1.5.2, ready for download. This version was mainly to resolve bugs, but we did manage to slip a couple new features in too:

– IE Java script fixes
– Re-added info icons (Lazy loading, Active, Passive, Notifications Disabled, etc.)
– Check_multi sanitize patch
– Log view fixed
– Missing commands (force host check)
– Fixed email validation – database upgraded to 254 characters
– Status map fixes

– Inherit rights at the group level
– Sort and grouping persistence in grids
– More info for notification view: Host, Service, Contact and Command (Email, SMS, etc.)
In the Icinga Reporting Cronk, the scheduling feature is now complete, which allows users to timetable reports to be sent or saved in the repository at certain dates or over reoccurring periods. The host/service selector has also been fixed so that services from a particular host can be selected.
The Icinga Web 1.5.x releases have been a whirlwind, so we thank you all for your patience, and especially for the bug reports and patches. Should anymore pop up, please get in touch either on the dev tracker or on the various support channels for help.

NEW: Icinga Reporting Cronk

Just last week we released version 1.5 with a standout new feature: Icinga Reporting in the New Web. Now you can view your SLA reports, host and service statuses all in the same place.
Essentially a Cronk pre-installed in the new web interface, Icinga Reporting consists of two tabs – ‘(On The Fly) Reporting’ and ‘Reporting Repository’ which offer in themselves handy reporting capabilities:

Run Reports in a Couple Clicks

In the Reporting tab, you can run reports on the fly with a couple of clicks. Simply select the report type, time frame and output format, then click on ‘Preview’ to view your report within seconds. 20 templates come delivered with the Icinga Reporting Package; so you can easily analyse your top 10 problematic hosts or services, availability reports, acknowledgement records and more.

Store & Retrieve User-Assigned Reports

In the Reporting Repository tab, the user can retrieve reports intended for them. As Icinga Reporting allows you to schedule reports to be run automatically, these can be either sent to the pre-defined recipient or deposited into a folder for them to access at a later time. Only authorized users may retrieve the reports from the repository – a useful function when reports need to be distinguished by customers or business units.

Scalable Report Generation & Distribution

Another feature that is useful for larger, enterprise environments is its ability to scale to multiple locations or monitoring instances. Icinga Reporting uses an external Jasper Server to generate and send reports in the right format, to meet pre-defined attributes. It can also manage multiple Jasper Servers and multiple Icinga instances for large-scale reporting.
Still haven’t given Icinga Reporting a try?
Demo it now or get started with the configuration guide.
Want to know more?
Read more on Icinga Reporting’s features and how Icinga Reporting works.
We’d like to thank Jaspersoft for their great tool (on which Icinga Reporting is based), the German BVA for their inspiration, and the Web/API team for their hard work!