Sound’s weird, but it is not. This year’s workshop of the German Nagios community took place in Nuremberg.
Beside a lot of other interesting projects around Nagios, the Icinga team had a chance to share our latest developments. Starting with a short status update of all project parts it was also a chance to give the audience a first impression of the upcoming reporting implementation.
Icinga Reporting is based on the IDO backend and just like the core, it will support all major database platforms. You can download all templates and the actual servlet implementation in our Git.
There was a lot of positive feedback and also a lot of ideas for the coming months until our final release in October. You can download the presentation here. Enjoy!
This week we finalized our release plan for the next few months. So far everything is going to plan, and we are on our way to shipping a unified, final version of Icinga Web, Core and Documentation in early October.
There will be additional releases in June and an intermediate version in August.
- 1.0.2 – 30 June 2010
- 1.0.3 – 18 August 2010
- 1.0.4 (unified stable release) – 6 October 2010
Hand in hand with the active community, contributors, our new team members and yourself, we will sprint to the finish line next month to extend and stabilize Icinga - and take it to the next level.
Check out our development system to follow our day-to-day progress.
At the end of March the Icinga Team will join the Open Source Expo in Switzerland. The Conference takes place from the 24th – 25th March in Bern and is the most popular event in the local open source business.
Beside other open source projects Icinga will take the chance to introduce the project, it’s goals and the future roadmap for the upcoming months. The Icinga Team would be happy to welcome you at our booth and will keep you informed from over there.
I am sure there will always be much discussion around the IDO-/NDOUtils database model. In my opinion there are two major problems with the model at the end of the day:
- Normalization
The tables have a lot of redundant information regarding their unique id’s. Different object types have a corresponding id and different object tables. To query a bunch of data you need to join the object and instance tables in most of the cases. This makes it hard to find a specific value without knowledge of the model.
- Prefix and table names
Icinga or Nagios as a prefix for every table makes no sense. The reason is that every supported database has schemas to store the tables and that is a better place to distinguish this. On the other hand we have a problem with Oracle to store tables with more than 30 characters.
In addition to that, some other problems like blocking, broker finetuning and loss of performance due to a lack of correct indices on the tables is hard work to do. At the moment, there is no time to change the whole model for every supported database and there is also a chance that the community has interesting suggestions worth first considering.
As a first step we want to introduce a new view layer based on the existing ndo model. A view is a “virtual” database object that queries the original data in the defined target table. I know this is not 100% true for every database, because we have various view types in oracle, but for now it is the only important thing. With this first early version we tried to solve these three issues:
- Every object table (which has an own object_type in the object_table) includes the correct object_id and a join to the instance table
- Every table is grouped into a configuration, historical and runtime area, which makes it easier to find a way through the model
- Every table has a grouped tablename for example ic_hosts_escs (icinga, configuration, hosts, escalation)
In an early stage of modeling I recognized that this will not be the final step and I decided to develop a code generator based on Java. Because it is a drop away thing, there was no focus on performance or style, so please forgive me. You can download the generator here as it is without any warranty.
Loading ...
You can download the first version of the view model here and run it against your database just check that your prefix is correct. We are looking forward to your feedback and also a rating on this idea.
Two days ago we presented the actual 1.0 Release an an early demo of the new webinterface at Open Source Monitoring Conference in Nuremberg here.
Here you can have a look on the presentation.
Demo for the alpha version will be available soon.
Nice weekend.
We just started the day with a great breakfast. Now everybody is set up, connected to the network and we are starting with a git workshop for everybody:
The agenda for today has a couple of task, e.g.:
- multi language documentation support
- quality review of our new web interface
- deployment and installation strategy for api and web interface
- further roadmap after the alpha release
Our wishes go to Michael Friedrich: He is ill and was not able to come. Get well soon.
A few minutes ago, nearly everybody of the Icinga Team arrived at the Linuxhotel in Essen. We have a big agenda for the weekend regarding the upcoming alpha release, the future release plan and various set of technical questions regarding all areas of the project.
Stay tuned for updates and pictures. Now it’s time for dinner.
We are planing to provide other databases than MySQL within the next Icinga Versions. Would you like to vote for your favourite database so that the Icinga Project fits your needs.
Loading ...
