Good front end tool for Nagios

[Brian A. Seklecki]

If you network has 2500 monitors, you can probably budget a developer to
write/develop a front-end that doesn't use PHP+MySQL, which are probably
the cause of your scalability issues.

Check out PosgreSQL.

~BAS

On Tue, 2007-06-12 at 13:27 -0400, Andrey Dmitriev wrote:
> All,
> 
> Is there are a good front end tool for Nagios that can 
> A) have profiles that we can apply to multiple hosts
> B) ideally stores in MySQL db (well, this is not really a requirement, 
> as apparently there are perl modules that can potentially load a mysql 
> db).
> 
> Please don't recommend Fruity/GroundWork, as apparently it pukes on 
> 2500+ monitors, or a certain number of hosts (at least GroundWork did 
> for us in version 4.51, which is why we plan to ditch it)
> 
> Thanks,
> Andrey
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
-- 
Brian A. Seklecki <bseklecki at collaborativefusion.com>
Collaborative Fusion, Inc.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null