Perhaps the memory portion of the esxtop output is not quite in the format that the hobbit backend understands. If you have access to a system and a top command that hobbit does understand, compare the output formats. If you can figure out a difference between them, you mighjt be able to code a sed filter to normalize the esxtop format data before passing it on to hobbit.

Thomas Kern 301-903-2211

----- Original Message ----- From: Ryan Sclanders <merlin_rbs at hotmail.com> To: hobbit at hswn.dk <hobbit at hswn.dk> Sent: Wed Jan 23 05:03:59 2008 Subject: [hobbit] esxtop

Hi All,

Was hoping someone could help me or at least steer me in the right direction when monitoring "memory usage" on an esx server. I have searched the web and newgroups only to find people talking about using esxtop and changing the hobbitclient-linux.sh script, when monitoring load and CPU. Unfortunately when changing the startup script to use esxtop the memory monitor column fails.

I considered writing a basic script to monitor the memory (example below), but am not sure how I would create the graphs to trend the mem usage. ################### #!/bin/sh

COLUMN=mem COLOR=green

cat /proc/vmware/mem |grep "Machine memory free" > /tmp/meminfo.txt

$BB $BBDISP "status $MACHINE.$COLUMN $COLOR date cat /tmp/meminfo.txt " exit 0 ###################

Does anyone have any better ideas or are doing anything different that could help resolve this dilemma?

Thanks in advance, Ryan

Who's friends with who and co-starred in what? http://www.searchgamesbox.com/celebrityseparation.shtml