From: Thilo Bangert <bangert@gentoo.org>
To: gentoo-server@lists.gentoo.org
Subject: cacti vs. munin was: [Re: [gentoo-server] apache2 segfaulting]
Date: Sat, 9 Dec 2006 19:22:40 +0100 [thread overview]
Message-ID: <200612091922.43001.bangert@gentoo.org> (raw)
In-Reply-To: <4579D03A.4000305@badapple.net>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
sorry for hijacking this thread.
> Additionally I'd
> start using cacti/snmp to watch system resources for tracking memory
> and load.
personally, i prefer munin for this kind of job. i started out on cacti,
which i favoured because it uses snmp, but when trying to get it to graph
more than just the basic stuff its complexity just was too much.
they do have a ton of plugins out there - but many of them seem to be
really hackish and difficult to get to work
with munin you can be up and running within minutes (on gentoo and debian
at least) and get so much more info out... and they too have a growing
number of plugins available.
kind regards
Thilo
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-12-09 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 17:57 [gentoo-server] apache2 segfaulting Grant
2006-12-08 20:51 ` kashani
2006-12-08 23:41 ` Grant
2006-12-09 18:22 ` Thilo Bangert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612091922.43001.bangert@gentoo.org \
--to=bangert@gentoo.org \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox