Thanks a lot for all the answers.
About my config, I have icinga classic 1.9.3 and also icinga web 1.8.3 (I'll
update it to 1.9.1 next week). Icinga web is used by 2-3 users and the other
are using the classic gui. I'll try to convince peaople to go for the new web
interface (with custom cronks to have a view on other kind of monitoring
systems and links), but I'll leave them the choice.
My IDO DB is on a dedicated (T4-2) servers, all in Ram, so this point will be
no problem in terms of performance.
The jasper part in on another dedicated VM centos server (but this part will
only be available to 5-10 users at the end of the project)
The main Icinga part is a HA active/active cluster (each server is 12 cores at
2.3Ghz (2xE2630) and 48Go RAm, HDD are poor sata):
- Master: Apache, drbd (on raid 5 sata), rrd(cached), icinga classic + ido2db,
10% of the checks, gearman server
- Slave: gearman workers for 90% of the checks
What I think I'll be doing next, as first steps:
- Put the status.dat and objects.cache on a Ram disk
- Upgrade Icinga-web to 1.9.1
- Create custom cronks and user roles so users will find Icinga-web as
something more great for them
- Try to convince users to use the web version
Regards,
Christophe
Disclaimer:
http://www.minfin.fgov.be/disclaimer.htm
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
