From: Haris Z. <ha...@eu...> - 2010-09-28 08:52:26
|
On 9/28/2010 8:32 AM, Nicolai Langfeldt wrote: > On 09/27/2010 02:43 PM, Haris Zukanović wrote: >> I need to measure different system values, like network bandwidth and >> CPU usage on the same single server but divided by client/account. I >> need to collect and show the graphs separated. I need also to let the >> client see only his own graphs and not those of other clients... >> >> I tried collecting separatly by running multiple munin-node processes on >> the same server each with it's own munin-config file and >> munin-data-folder. It would allow me to enable/disable plugins per >> client. >> ... but it does not work. I think there may be a bug in munin-node >> >> I start munin-node with my own config customised >> /usr/sbin/munin-node --config="/etc/munin-haris/munin-node.conf" >> Pid_file already exists for running process (10741)... aborting >> >> but it complains about pid file even though I set a unique pid_file in >> my config file, unique TCP port and so on... > > That would seem to be a bug. It seems not be registered in trac. I registered it. > > > Aside from this initial problem which I think can easily be resolved, > > please advise me if this is the right approach to divide collecting > data > > by client/account? > > No, you have worse problems than the pid. As far as I know there is > simply no way to get cpu, memory and network traffic accounted for by > user. If your application lends itself to be installed in one VM pr. > user you need to account for then you can measure each VM intimately > though. > I am aware of this and I think I may have to customise some of the plugins I intend to use. It will be no problem. > You may be able to write a plugin to do pr. unix-uid accounting with > something like sar (system accounting) - it will have cpu and memory, > and as far as I recall disk i/o stats. > >> Also, how can I separate clients in the web graph interface? Which is >> the right way? Do I need to run multiple instances of server or can this >> be done somehow? > > The simplest way would be to configure separate user lists with > passwords for each appropriate part of the munin html/png hierarchy. I suppose you mean controlling with .htaccess It would not be a adequate solution since there could be many servers in the entry page and only 1 or 2 belonging to the client in question. I was wondering if munin had any way of controlling (separating) what user can see when he "logs in". If not, I think the only way of effectively separating is to run separate munin servers with customised /usr/bin/munin-cron for each client? > >> This e-mail and any file transmitted with it may contain material that >> is confidential, privileged for the sole use of the intended recipient. > > I have no idea how to discern if your email contained confidential > information. Please advice. I am sorry about this message, it is a company policy to have it. Please risregard it since I have intentionally sent the message to the munin mailing list for everyone to be able to read. > >> You >> should not copy or use it for any purpose, disclose the contents of the >> same to any other person or forward it without express permission. > > You did not give me express permission to copy or use your email for > the purposes of answering your query. I suspect that I might need to > stay away from italy now? Nicolai, I am sorry about this, I know it can sound silly. Please disregard > > Regards, > Nicolai Thank you for the answers -- Haris Zukanovic CEO <http://www.eu-softing.com> SOFTING d.o.o. K.M. Visevica Humskog, 12, 88000 Mostar, Bosnia and Herzegovina Tel. +387 36 318 339- Mob. + 387 61 839 069 - Fax. +387 36 318 339 ha...@eu... <mailto:ha...@eu...> - www.softing.ba <http://www.softing.ba> - SkypeID: hara.mostar P* lease consider our environment before printing this e-mail* ------------------------------------------------------------------------ This e-mail and any file transmitted with it may contain material that is confidential, privileged for the sole use of the intended recipient. If you are not the intended recipient of this e-mail, please do not read this e-mail and notify us immediately by reply e-mail or by telephone and then delete this message and any file attached from your system. You should not copy or use it for any purpose, disclose the contents of the same to any other person or forward it without express permission. Considering the means of transmission, we do not undertake any liability with respect to the secrecy and confidentiality of the information contained in this e-mail and in its attachments. Il presente messaggio di posta elettronica e ogni eventuale documento a quest'ultimo allegato potrebbe avere carattere riservato ed essere tutelato ed è ad esclusivo utilizzo del destinatario indicato in indirizzo. Qualora non foste il destinatario del presente messaggio Vi preghiamo di volerci avvertire immediatamente tramite posta elettronica o telefonicamente e di cancellare il presente messaggio e ogni documento ad esso allegato dal Vostro sistema. E' vietata la duplicazione o l'utilizzo per qualunque fine del presente messaggio e di ogni documento ad esso allegato così come la relativa divulgazione, distribuzione o inoltro a terzi senza l'espressa autorizzazione del mittente. Il mittente, in ragione del mezzo di trasmissione utilizzato, non assume alcuna responsabilità in merito alla segretezza e riservatezza delle informazioni contenute nel presente messaggio e nei relativi allegati. |