public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: How to record memory usage & bandwidth usage?
Date: Tue, 11 Oct 2011 18:05:16 +0000 (UTC)	[thread overview]
Message-ID: <loom.20111011T194912-98@post.gmane.org> (raw)
In-Reply-To: CAA2qdGXBpJsr7KvK9y1YiNmcNHnVruVZOnLKQmpUiyh3xGUdJQ@mail.gmail.com

Pandu Poluan <pandu <at> poluan.info> writes:


> The head honcho of my company just asked me to "plan for migration of
> X into the cloud" (where "X" is the online trading server that our
> investors used).

This is a single server or many at different locations.
If a WAN monitoring is what you are after, along with individual
server resources, you have many choices.

> Now, I need to monitor how much RAM is used throughout the day by X,
> also how much bandwidth gets eaten by X throughout the day.

Most of the packages monitor ram as well as other resource utilization
of the servers, firewall, routers and other SNMP devices in your network.
some experimentation may be warranted to find what your team likes best.

> What tools do you recommend?

OH boy. I like JFFNMS very very much. It has a very old version in portage
(masked) but a very new version out there for Debian and Ubuntu. It 
runs on all nix, if you want to driectly compile and install.

I'll be putting together a new ebuild, as soon as I get it working
with the latest postgresql. Mysql works out of the box. Postgresql-9
has many new and very cool features.

> Remember: The data will be used for 'post-mortem' analysis, so I don't
> need any fancy schmancy presentation. Just raw data, taken every N
> seconds.

Personally, I have some large, high risk design work going on. JFFNMS
and pg9 are the best choices from my research. A whiz like yourself
could easily look at the old JFFNMS ebuild and create a new one.
PG-9 (please no flame wars on mysql vs pg9) is very cool and what
my work is migrating too, once I get some breathing room.

Craig at jffnms.org is very cool and responsive. He also works closely
with those that submit patches. Nagios is a large, disorder array that
had many devs fork off since the project leader (was/is an a_ole)
is quite difficult to work with.

JFFNMS rules and is very cool for managing cisco and other routers,
not to mention a myriad of snmp(1,2.3) devices and all types
of servers. The original guy, Javier, was snapped  up by someone
worth billions, to manage and extend his financial network, but, Craig
is probably stronger coder, and extraordinarily nice human being.
It's mostly php. Lots of folks extend JFFNMS, Craig keeps it clean
and well written and documented code.

http://www.jffnms.org/

hth,
James








  parent reply	other threads:[~2011-10-11 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11  9:48 [gentoo-user] How to record memory usage & bandwidth usage? Pandu Poluan
2011-10-11 10:21 ` Mick
2011-10-11 10:35   ` Matthew Marlowe
2011-10-11 18:05 ` James [this message]
2011-10-26  1:27   ` [gentoo-user] " Pandu Poluan
2011-10-26  1:33     ` Pandu Poluan
2011-10-26  1:52     ` kashani
2011-10-26  2:31       ` Pandu Poluan

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=loom.20111011T194912-98@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@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