Nagios is dead! Long live Icinga!

Hendrik Baecker andurin at process-zero.de
Thu May 7 18:52:33 CEST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Andreas Ericsson schrieb:
> Hendrik Baecker wrote:
>> Andreas Ericsson schrieb:
>> I hope so, I realy don't want to loose all my commits on icinga.
> 
> Ah, so you're using git already?
> 
Yes, we are on git and I have to say I love it more from day to day. A
SCM that really can handle branches and merges. Wonderfull and fits
perfectly for bigger developer bases.

>>> I hope Icinga forks from that DSCM, and uses the same DSCM to
>>> maintain their own code so that a future merge becomes as painless
>>> as possible.
>> Icinga forked from a cvs2git copy, so future merging might be possible.
>>
> 
> It would even be trivial if that cvs2git repository is available for
> cloning :-)
> 
Call me insane, but I'm afraid to lose face with publishing a half ready
code base, even if I know that I can lose it when you read my 1527
commit messages *just kidding*.
> 
>> As I mentioned before. Code base will be opened in the next days as a
>> pre-alpha, mega-super-testing phase ;)
>> No, it's not only a political stunt to get Ethan to wake up again.
> 
> mega-super-testing is fine, so long as it's code :p
> 
Be patient with my face ;)

> 
> Including object sizes and layout? If so, you're doing something good
> and something bad at the same time.
> There's room for improvement in the objects in Nagios today. A lot of
> integer flags can (and should) be removed and reworked into bitmasks.
> That would make matching them against their dependencies and contacts'
> options trivial
> 
>   if (1 << host->state & contact->notify_options & host->notification_options)
>     send_host_notification(host);
> 
I know you are some kind of magician but primary goal is to be more open
to be able to share the work on more shouldes.
>> The next steps should be a open development of the blocking ndoutils
>> and better db abstraction.
> 
> I know you've taken a look at merlin (though I don't know if you saw the
> figures of the NDOUtils scalability testing we did). Any reason you chose
> to move forward with NDOUtils? Or is the database schema chopped into a
> more scalable form as well?
> 
I am a huge amount of commits behind the actual version and I love your
idea behind it.
Correct me if I'm wrong but merlin wasn't designed as a better ndo2db,
wasn't it? Up to know it looks more like a benefit for monitoring
performance improvements like DNX (in the scope of delegate the checking
work), in this thoughts I don't understand why I should have to use
merlin to fill a database?
Even if the ndoutils db scheme is a complex one I believe that it is
possible to tweak it for better performance.
NDOUtils are old enough to have an established userbase already (NagVis
and some other more or less good reporting tries for example).

In short, ndoutils is somewhat like a already givven solution for those
who defines that using a database is mandatory.
If you know someone who has a more simple but faster solution to get
nagios data to a database without a bypass over another entity which
already has another mission - let's talk about it.
NDO DB Scheme isn't a must have for me, but for the moment it's the best
thing (ignoring the bottlenecks) to bring nagios data directly to a
database.

- -
Hendrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkoDEdEACgkQlI0PwfxLQjlF7ACeM6e7Qi6QDZnCrgnTRbSG0HvW
qEMAn2QkB1GPuL+VNaNGU0NFKkFlAcRu
=STtR
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com




More information about the Developers mailing list