1 |
(Sorry for the late reply; somehow this thread got lost in the mess) |
2 |
|
3 |
On Oct 12, 2011 2:03 AM, "James" <wireless@×××××××××××.com> wrote: |
4 |
> |
5 |
> Pandu Poluan <pandu <at> poluan.info> writes: |
6 |
> |
7 |
> |
8 |
> > The head honcho of my company just asked me to "plan for migration of |
9 |
> > X into the cloud" (where "X" is the online trading server that our |
10 |
> > investors used). |
11 |
> |
12 |
> This is a single server or many at different locations. |
13 |
> If a WAN monitoring is what you are after, along with individual |
14 |
> server resources, you have many choices. |
15 |
> |
16 |
|
17 |
It's a single server that's part of a three-server system. The server needs |
18 |
to communicate with its 2 cohorts continuously, so I have to provision |
19 |
enough backhaul bandwidth from the cloud to my data center. |
20 |
|
21 |
In addition to provisioning enough RAM and CPU, of course. |
22 |
|
23 |
> > Now, I need to monitor how much RAM is used throughout the day by X, |
24 |
> > also how much bandwidth gets eaten by X throughout the day. |
25 |
> |
26 |
> Most of the packages monitor ram as well as other resource utilization |
27 |
> of the servers, firewall, routers and other SNMP devices in your network. |
28 |
> some experimentation may be warranted to find what your team likes best. |
29 |
> |
30 |
|
31 |
Currently I've settled on a simple solution: run dstat[1] with nohup 30 |
32 |
minutes before 1st trading session, stop it 30 minutes after 2nd trading |
33 |
session, and send the CSV record via email. Less intrusion into the system |
34 |
(which the Systems guys rightly have reservations of). |
35 |
|
36 |
> > What tools do you recommend? |
37 |
> |
38 |
> OH boy. I like JFFNMS very very much. It has a very old version in portage |
39 |
> (masked) but a very new version out there for Debian and Ubuntu. It |
40 |
> runs on all nix, if you want to driectly compile and install. |
41 |
> |
42 |
> I'll be putting together a new ebuild, as soon as I get it working |
43 |
> with the latest postgresql. Mysql works out of the box. Postgresql-9 |
44 |
> has many new and very cool features. |
45 |
> |
46 |
|
47 |
Cool! I *love* Postgresql! Update me when the ebuild's done? |
48 |
|
49 |
> > Remember: The data will be used for 'post-mortem' analysis, so I don't |
50 |
> > need any fancy schmancy presentation. Just raw data, taken every N |
51 |
> > seconds. |
52 |
> |
53 |
> Personally, I have some large, high risk design work going on. JFFNMS |
54 |
> and pg9 are the best choices from my research. A whiz like yourself |
55 |
> could easily look at the old JFFNMS ebuild and create a new one. |
56 |
|
57 |
Naaah, I'm going to wait for your ebuild. I'm sometimes lazy, you know ;-) |
58 |
|
59 |
> PG-9 (please no flame wars on mysql vs pg9) is very cool and what |
60 |
> my work is migrating too, once I get some breathing room. |
61 |
> |
62 |
> Craig at jffnms.org is very cool and responsive. He also works closely |
63 |
> with those that submit patches. Nagios is a large, disorder array that |
64 |
> had many devs fork off since the project leader (was/is an a_ole) |
65 |
> is quite difficult to work with. |
66 |
> |
67 |
|
68 |
That sounds really cool. I've been hesitant to go the Nagios route because |
69 |
of the mess. I'll sure to be checking out JFFNMS. |
70 |
|
71 |
> JFFNMS rules and is very cool for managing cisco and other routers, |
72 |
> not to mention a myriad of snmp(1,2.3) devices and all types |
73 |
> of servers. The original guy, Javier, was snapped up by someone |
74 |
> worth billions, to manage and extend his financial network, but, Craig |
75 |
> is probably stronger coder, and extraordinarily nice human being. |
76 |
> It's mostly php. Lots of folks extend JFFNMS, Craig keeps it clean |
77 |
> and well written and documented code. |
78 |
> |
79 |
> http://www.jffnms.org/ |
80 |
> |
81 |
> hth, |
82 |
> James |
83 |
> |
84 |
|
85 |
Thanks for the heads-up! Although the original problem is solved already |
86 |
(granted, in a somewhat kludgy way), your post is a great write-opener! Much |
87 |
appreciated :-) |
88 |
|
89 |
Rgds, |