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 ...
We’ve just released the first beta version of Icinga and just a couple of hours later, the first version for Mac OS X is online. Thank you for this excellent work. You can download Icinga 0.8.0 for Leopard here.
P.S. There is also a Nagios Version for Mac available.
Like Hendrik promised yesterday we want to open our tracking-system to the public, to give ”everybody” a chance to contribute and send a patch- or featurerequest.
This is done now and you can reach the tracker on our development-platform. All steps needed for issue creation are documented in our development-wiki.
Feel free to send us your feedback, bugs and ideas to make Icinga more better.
A group of leading Nagios protagonists including members of the Nagios Community Advisory board and creators of multiple Nagios Addons have launched Icinga – a fork of Nagios, the prevalent open source monitoring system. This independent project strives to be more responsive to user requests and faster in software development through the support of a broader developer community.
The new open source monitoring system will be fully compatible with its predecessor, retaining all the existing Nagios features while adding new features requested by the Nagios user community. Long standing bugs will be removed and improvements will be made, especially for the database integration alongside a standardised API to simplify the integration of 3rd party addons. Icinga will also be developed to include an improved functionality in large and complex environments.
Built on proven technologies and concepts as well as progressive frameworks and standards, Icinga is a product of the community – their ideas, needs and combined passion for innovation.
Icinga takes all the great features of Nagios and combines it with the feature requests and patches of the user community. These modifications hail direct from the community and are supported by the concrete experiences of those involved in customer projects.
The first releases are expected for the end of May. The first stable Version is scheduled for October 28th.
