[icinga-devel] Icinga web interface

Frank.Belau at o-s.de Frank.Belau at o-s.de
Tue Jun 2 17:01:18 CEST 2009


Ich bin zwar auch ein Freund von einzelnen configfiles für jedes System, aber bei uns ist es so, daß die Administratoren, die sich um das Monitoring kümmern, nur die Server in die Monitoringumgebungen aufnehmen. Der Admin des zu überwachenden Servers, stellt sich die Schwellwerte selbst ein. Ich möchte jetzt mal nicht darauf eingehen, ob das so nun sinnvoll ist oder nicht. 
Da wir nicht nur Linux-Umgebungen haben, sondern auch HPUX, AIX und vor allem sehr viele Windowsumgebungen, ist es schon ein sehr hoher Aufwand die vielen Windowsadmins in der Benutzung des vi zu schulen. Hier wäre es sehr sinnvoll, wenn es eine einfach zu bedienende Webschnittstelle geben könnte, mit der auch Windows-Admins zurechtkommen. Damit könnten alle Admins sehr gut leben.

PS: schnelle Googleübersetzung:
Although I am a friend of each configfile for each system, but for us it is so that the administrators who are concerned about the monitoring of care, only the servers in the monitoring environments to take. The admin of the server to be monitored, there is the threshold itself. I would now not be received, whether this makes sense now or not.
Because we do not just Linux environments, but also HPUX, AIX, and above all, very many Windows environments, it is already a very high burden to many Windows admins to use the vi trained. Here it would be very useful if it is an easy to use web interface could, even with the Windows admins cope. This could all very well Admins live.

Mit freundlichen Grüßen, iXware 

> -----Ursprüngliche Nachricht-----
> Von: Martin Fuerstenau [mailto:mf at maerber.de] 
> Gesendet: Dienstag, 2. Juni 2009 16:11
> An: icinga-devel at lists.sourceforge.net
> Betreff: Re: [icinga-devel] Icinga web interface
> 
> I agree totally. Due to the fact that we has to deal with 
> config files I think the main problem of most tools is that 
> the "oldfashioned big monster files" are generated from the 
> tools. Impossible to add for example 50 hosts with all 
> services by hand.
> 
> And templates are also not a solution except you are a 
> internet provider or so.
> 
> I prefer a directory structure. One directory per server at 
> the end with one file per service in each directory. This 
> works fine for 1300 hosts and 9000 services. Impossible to 
> handle that with a webfrontend.
> 
> Greetings
> Martin Fuestenau
>  
> On Tue, 2009-06-02 at 15:22 +0200, berny1 at users.sourceforge.net wrote:
> > Hello everybody,
> > 
> > > > Providing an API which other people can build a quality web 
> > > > interface from seems to be the most flexible solution; 
> requiring 
> > > > people to configure things through the Icinga web 
> interface "only" 
> > > > would be a mistake, most things like Centreon are 
> *horrible* and nasty.
> > > >
> > > > It's very difficult to provide a web interface which copes with 
> > > > the requirements of a large environment, particularly all the 
> > > > masses of service dependencies and host dependencies 
> you may have 
> > > > :)
> > > 
> > > Thanks for the explanation, but my boss want web intarface 
> > > configuration, so i will stay with Centreon :-) It seems 
> quite well 
> > > so far.
> > 
> > For big installations, I think, most admins would prefer 
> config files because configuration can be done in less time. 
> You can easyly copy and past or you can generate parts of the 
> configuration files by script e. g. from an inventory database or so.
> > 
> > For installations with only a view servers and view changes 
> maybe someone might find a GUI helpful, because he does not 
> need to know about the syntax of the config files.
> > 
> > So I think, the idea Julian posted is a very good idea.
> > 
> > Bernd
> > 
> > 
> > 
> ----------------------------------------------------------------------
> > -------- OpenSolaris 2009.06 is a cutting edge operating system for 
> > enterprises looking to deploy the next generation of Solaris that 
> > includes the latest innovations from Sun and the OpenSource 
> community. 
> > Download a copy and enjoy capabilities such as Networking, 
> Storage and 
> > Virtualization.
> > Go to: http://p.sf.net/sfu/opensolaris-get
> > _______________________________________________
> > icinga-devel mailing list
> > icinga-devel at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/icinga-devel
> > 
> 
> 
> This message and attachment(s) are intended solely for use by 
> the addressee and may contain information that is privileged, 
> confidential or otherwise exempt from disclosure under applicable law.
> 
> If you are not the intended recipient or agent thereof 
> responsible for delivering this message to the intended 
> recipient, you are hereby notified that any dissemination, 
> distribution or copying of this communication is strictly prohibited.
> 
> If you have received this communication in error, please 
> notify the sender immediately by telephone and with a 'reply' message.
> 
> Thank you for your co-operation.
> 
> 
> 
> --------------------------------------------------------------
> ----------------
> OpenSolaris 2009.06 is a cutting edge operating system for 
> enterprises looking to deploy the next generation of Solaris 
> that includes the latest innovations from Sun and the 
> OpenSource community. Download a copy and enjoy capabilities 
> such as Networking, Storage and Virtualization. 
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> icinga-devel mailing list
> icinga-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/icinga-devel
> 




More information about the icinga-devel mailing list