Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 073C19FB25B for ; Sun, 25 Mar 2007 02:46:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 72656-08 for ; Sun, 25 Mar 2007 02:46:18 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237]) by postgresql.org (Postfix) with ESMTP id F1C6E9FB1CE for ; Sun, 25 Mar 2007 02:46:19 -0300 (ADT) Received: by wr-out-0506.google.com with SMTP id 70so476171wra for ; Sat, 24 Mar 2007 22:46:19 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ujV5hFYRnj2VVngXsEnE1SLsvNlGR185qKXzpSc2jOzo5lEavUBHsBlb2iTzKcBMM4a0RBFOdiFq0gTdL0KLgKCJ/0RdcIynBOPe4weTEIZdgD6ok0p7TO7AYQ3jK0jHXEoW2JBbFTBJIL/Kw8Qr/vmyT/AxG1UHgCqN9NLZiwU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=bhcSOs5sqEe39voebHHV9Zn8kAcF0oCjM7k8fg0H6nv5GqIpqRy3D12XqnAlEbSLBnQGs/5HcABUCjnrjHjhvRl6e1QiSgaUL7pRpQSDeAq4NwCmvhNJ36T/edJk6qcrmurnbVVxkWzF2inQK6K+/AELXRnNu3sHIXEI65aAyoI= Received: by 10.114.107.19 with SMTP id f19mr1991103wac.1174801577957; Sat, 24 Mar 2007 22:46:17 -0700 (PDT) Received: by 10.114.120.13 with HTTP; Sat, 24 Mar 2007 22:46:17 -0700 (PDT) Message-ID: <467669b30703242246gfac2ff5h66b5723d923520f0@mail.gmail.com> Date: Sat, 24 Mar 2007 22:46:17 -0700 From: "CAJ CAJ" To: "Erik Jones" Subject: Re: OT: Munin (was Re: Determining server load from client) Cc: "Tobias Brox" , "Richard Huxton" , "Joe Healy" , "Dan Harris" , "PostgreSQL Performance" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_235711_21291696.1174801577861" References: <460080A2.20800@drivefaster.net> <46008931.8060605@omc-international.com.au> <4600E13F.3070806@archonet.com> <20070321101340.GI10137@oppetid.no> <2B568D22-BDCC-40B7-B27D-0F47216094F2@myemma.com> <20070321211305.GA29211@oppetid.no> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/391 X-Sequence-Number: 23796 ------=_Part_235711_21291696.1174801577861 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 3/21/07, Erik Jones wrote: > > > On Mar 21, 2007, at 4:13 PM, Tobias Brox wrote: > > [Erik Jones - Wed at 09:31:48AM -0500] > > I use cacti (http://cacti.net) which does the same thing that munin > does but in php instead. Here's what I use to db stats to it (again, > php): > > > I haven't tried cacti, but our sysadm has done a little bit of research > and concluded "cacti is better". Maybe some day we'll move over. > > Munin is generating all the graphs statically every fifth minute, while > cacti generates them on demand as far as I've understood. The munin > approach is pretty bloat, since one usually would watch the graphs much > more seldom than what they are generated (at least, we do). That's not > really an argument since CPU is cheap nowadays - but a real argument is > that the munin approach is less flexible. One would like to adjust the > graph (like, min/max values for both axis) while watching quite some > times. > > > Well, by "default", Cacti polls all of the data sources you've set up > every five minutes as well as that's how the docs instruct you to set up the > cron job for the poller. However, with a little understanding of how the > rrdtool rras work, you could definitely poll more often and simply edit the > existing rras and datasources to expect that or create new ones. And, yes, > the graph customization is pretty cool although for the most part the just > map what's available from the rrdtool graph functionality. If you do decide > to set up Cacti I suggest you go straight to the faq section of the manual > and read the part about going from a simple script to a graph. The main > manual is almost entirely centered on the built-in networking (e.g. snmp) > data sources and, as such, doesn't do much for explaining how to set up > other data sources. > Has anyone had experience setting up something similar with Nagios? We monitor servers using nagios and not having to install additional software (cacti/munin) for postgres resource usage monitoring would be great. Thanks in advance! ------=_Part_235711_21291696.1174801577861 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 3/21/07, Erik Jones <erik@myemma.com> wrote:

On Mar 21, 2007, at 4:13 PM, Tobias Brox wrote:

[Erik Jones - Wed at 09:31:48AM -0500]
I use cacti (http://cacti.net) which does the same thing that munin  
does but in php instead.  Here's what I use to db stats to it (again,  
php):

I haven't tried cacti, but our sysadm has done a little bit of research
and concluded "cacti is better".  Maybe some day we'll move over.

Munin is generating all the graphs statically every fifth minute, while
cacti generates them on demand as far as I've understood.  The munin
approach is pretty bloat, since one usually would watch the graphs much
more seldom than what they are generated (at least, we do).  That's not
really an argument since CPU is cheap nowadays - but a real argument is
that the munin approach is less flexible.  One would like to adjust the
graph (like, min/max values for both axis) while watching quite some
times.

Well, by "default", Cacti polls all of the data sources you've set up every five minutes as well as that's how the docs instruct you to set up the cron job for the poller.  However, with a little understanding of how the rrdtool rras work, you could definitely poll more often and simply edit the existing rras and datasources to expect that or create new ones.  And, yes, the graph customization is pretty cool although for the most part the just map what's available from the rrdtool graph functionality.  If you do decide to set up Cacti I suggest you go straight to the faq section of the manual and read the part about going from a simple script to a graph.  The main manual is almost entirely centered on the built-in networking ( e.g. snmp) data sources and, as such, doesn't do much for explaining how to set up other data sources.


Has anyone had experience setting up something similar with Nagios? We monitor servers using nagios and not having to install additional software (cacti/munin) for postgres resource usage monitoring would be great.

Thanks in advance!


------=_Part_235711_21291696.1174801577861--