[op5-users] Ninja backend and architecture

Hendrik Baecker andurin at process-zero.de
Tue Mar 31 10:23:00 CEST 2009


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



Andreas Ericsson schrieb:
> Matthias Flacke wrote:
>> Can you explain your decision a bit more? We all know about
>> constraints and weaknesses in NDO. But was performance the only
>> reason to create a proprietary DB model and leave the compatibility
>> path for all addons based on NDO?
>>
> 
> Not entirely. The new database model is also a lot simpler to
> understand and write queries for. Those two sort of go hand in hand
> though, since complex queries are often very difficult to optimize
> well, and difficult to create an optimized database for.
> 
> However, the primary reason we didn't stick with NDOUtils is that
> it doesn't scale linearly, and we failed to find a way to fix that.
> In other words, a query against a database with 100 services may
> take 1 second, but if you increase the number of services to 1000,
> the same query takes somewhere around 50 or 60 seconds instead of
> the expected 10. This behaviour can be seen relatively early, and
> indicates that the database model just won't work in a network with
> oh, let's say 50000 services.
> 
hm... are you talking about INSERT/UPDATE queries or SELECTs?
I'm just playing with the NDO db scheme and I was able to SELECT 10.000
Nagios objects (5000 Hosts / 5000 Services) in less than 10 seconds.
Skill-Level 2: It was a join select over six or seven tables with the
spoken query: "Show me all host||service status for which I am
authorized for."
I would say, getting the data isn't such a big problem if you know your
enemy ;)
But I agree with you that data input is a huge problem in current NDOUtils.
Most of us have already seen a staling nagios monitoring because of a
overworked database/ndo2db situation.

If you are interested in more detail, contact me off-list since
discussion that would be off-topic here.

To the rest of Ninja [btw: A realy good name ;) ]:
I love the idea of a new Web Interface. Your thought about different
widget handling to get a modular framework is awesome!
But for the most of the nagios users out there nagios is complex enough.
Why building another dependency on other software like Merlin?
I would appoligize to be straight forward, but I think everyone want's
to have a new WebUI but only middle up to huge environments will benefit
from merlin.
I were realy excited to contribute to ninja, but I fear the merlin
dependency as another failuresource in the nagios workflow.

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

iEYEARECAAYFAknR0uQACgkQlI0PwfxLQjkBFQCfe3iCOWoM41jJ6XEuqR832bTC
n9kAnA9F2KGBqU99iwRyIDJFKPSBm8CW
=i2/d
-----END PGP SIGNATURE-----


More information about the op5-users mailing list