[Kolab-devel] munin

Gunnar Wrobel wrobel at pardus.de
Wed Mar 26 08:26:15 CET 2008

Hi Richard,

Richard Bos <ml at radoeka.nl> writes:

> Hi,
> this week I have installed an application called munin.  It is a (from the 
> website) monitoring tool to survey all your computers and remembers what it 
> saw. It presents all the information in graphs through a web interface.  
> (more information at: http://munin.projects.linpro.no/ and look for about 
> munin).
> I like the way it present the information, but even more the easiness of 
> installation.  On openSUSE the only thing I needed to do, was to install the 
> rpms (the package manager took care of the dependencies ;) ).
> With Munin this idea
> http://wiki.kolab.org/index.php/Soc_2006#Kolab_centralized_log_management_and_analisys
>  is implemented :)
> Although I don't have the figures yet for amavis, clamav, openldap and 
> spamassassin (did I forget a service?).  However, I just discovered munin 
> exchange: http://muninexchange.projects.linpro.no/
> It has plugins for clamav, openldap and amavis.  I'll soon install the 
> openldap one.  Unfortenately a plugin for cyrus is missing.  Does anyone now 
> how to obtain figures of cyrus' performance?  Does someone have a cyrus 
> plugin for munin?
> Last: I think that munin would be a great application to add to the kolab 
> server, especially when it comes with the additional plugins for the services 
> that are used by kolab.  I think that it would be rather easy to even 
> configure (add) slaves automatically to the config file of the main munin 
> host (using kolab's template mechanism).  If intergrated, it would be nice it 
> it is part of kolab manager login.
> Example munin output: http://munin.ping.uio.no/
> Just to let you know, that this application exists and seems usefull to kolab 
> admins.

munin is definitely a very useful tool and I think using it with the
Kolab server makes a lot of sense.

Adding it to the set of features provided by the core Kolab server is
a different thing though. We'll get the same problem as with grey
listing: The Kolab server already has a rather large set of features
that is hard to support in its entirety. Each extra application would
add a good deal of additional features that would also need testing
and support. Given the current man power behind the project we should
definitely be careful about that.

That being said I believe we need a good extension/plugin possibility
that allows to provide such additional features/applications.

And the good news: I'm pretty certain I found a nice solution that
even accommodates for the fact that we are all working with Kolab on
different distributions. I'm currently testing it with Kolab2/Gentoo
and will propose it as an alternative to the current kolabconf if
testing looks promising.



> -- 
> Richard Bos
> Without a home the journey is endless
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 

More information about the devel mailing list