Releasing Icinga Reporting for Early Adopters

Releasing Icinga Reporting for Early Adopters

We’re happy to announce that we released an early version of Icinga Reporting today! With this release we create the foundation for an overall reporting functionality for Icinga by introducing a new way to work with collected data. At the same time we are also publishing the first use case of Icinga Reporting which enables you to calculate, display and export SLA reports for your hosts and services.

 

Icinga Reporting

Icinga Reporting is the framework and foundation we created to handle data collected by Icinga 2 and other data providers. By definition Icinga Reporting does not collect or calculate any data. The framework processes usable data from data providers such as Icinga’s IDO or Icinga Web 2 modules and makes them available in different formats. The first version can display the data directly within the Icinga web interface or export it to PDF, JSON or CSV format. With scheduled reports you can receive the prepared data periodically via email.

 

IDO Reports

The IDO is the database where Icinga 2 stores all the status data it collects. It is also the first data provider for Icinga Reporting. We calculate the availability of your hosts and services over a certain amount of time and return a percentage value. This allows you to evaluate and compare the accessibility of you applications and network devices. You can use the data to check if you’re meeting your SLA (Service-Level-Agreement) and share it with your team and managers.

 

Open Source Projects

Icinga Reporting consists of multiple projects. We’re continuously working on updating and extending our existing Modules to provide data for Icinga Reporting. This release is at a very early stage and your feedback is very welcome and appreciated.

Join our community on community.icinga.com and have a chat with us about your reporting use cases and challenges! We will discuss Icinga Reporting on our upcoming Icinga Camps as well. The CfP for Stockholm, Milan and Zürich is still open for those who are interested in speaking at these events.

 

 

 

 

 

 

 

 

 

 

 

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.
Changelog:

  • 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:

Fixes
– 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

Features
– 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.