|
amadmin and amplot analysis
2003-01-07 04:36:51
I am starting to look at the utilities amadmin and amplot. The
following is my attempt to get some perspective on post analysis. Has
anyone has written notes/docs related to the display of AMANDA's data
metrics or performed post-analysis of the data? If so, I would like
to read them.
I noticed that the output of the following amadmin command differed
substantially between versions 2.4.2 and 2.4.3-20030104. For example:
amadmin <config> amdump.1
2.4.2 produced m,any lines of output, such as:
amplot -e amdump.1
Displaying graph on the screen, <CR> for next graph
20030103 INFO# dumper: dgram_bind: socket bound to 0.0.0.0.537
20030103 INFO# dumper: dgram_bind: socket bound to 0.0.0.0.539
20030103 INFO# dumper: dgram_bind: socket bound to 0.0.0.0.538
20030103 INFO# dumper: dgram_bind: socket bound to 0.0.0.0.541
20030103 INFO# dumper: stream_client: connected to 128.3.132.16.34299
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1538
20030103 INFO# dumper: stream_client: connected to 128.3.132.16.34300
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1539
20030103 INFO# dumper: stream_client: connected to 128.3.132.16.34301
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1540
20030103 INFO# dumper: stream_client: connected to 128.3.28.26.4379
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1541
20030103 INFO# dumper: stream_client: connected to 128.3.28.26.4380
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1542
20030103 INFO# dumper: stream_client: connected to 128.3.28.26.4381
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1543
20030103 INFO# dumper: stream_client: connected to 128.3.28.25.1544
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1548
20030103 INFO# dumper: stream_client: connected to 128.3.132.98.1124
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1547
[ 80+ lines deleted for brevity ]
20030103 INFO# dumper: stream_client: connected to 128.3.28.25.1659
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1662
20030103 INFO# dumper: stream_client: connected to 128.3.28.25.1660
20030103 INFO# dumper: stream_client: our side is 0.0.0.0.1663
Longest dumping hosts Times 10800
Host:disk/lev start - end = run => total
redbelly:/net/adder/scratch2/2 0:14:50 - 0:14:51 = 0:00:01
redbelly:/usr/local_redbelly/etc/1 0:15:05 - 0:15:06 = 0:00:01
redbelly:/etc/1 0:15:47 - 0:15:47 = 0:00:00
redbelly:/var/amanda/1 0:16:01 - 0:16:03 = 0:00:02
redbelly:/net/redbelly/lanl1/1 0:16:17 - 0:16:20 = 0:00:03
redbelly:/net/redbelly/home1/1 0:16:31 - 0:16:40 = 0:00:09
redbelly:/net/adder/scratch1/0 0:16:46 - 2:38:27 = 2:21:41
redbelly:/net/redbelly/lbnl1/0 2:38:28 - 5:04:48 = 2:26:20 => 4:48:17
anaconda:/etc/1 0:14:51 - 0:14:52 = 0:00:01
anaconda:/net/anaconda/scratch1/1 0:15:07 - 0:15:47 = 0:00:40
=> 0:00:41
Whereas, with the 2.4.3-20030104 version, the output did not display
that stuff above.
amplot -e amdump.1
Displaying graph on the screen, <CR> for next graph
Longest dumping hosts Times 10800
Host:disk/lev start - end = run => total
redbelly:2/1048576 0:14:50 - 0:14:51 = 0:00:01
redbelly:1/1048576 0:15:05 - 0:15:06 = 0:00:01
redbelly:1/1048576 0:15:47 - 0:15:47 = 0:00:00
redbelly:1/1048576 0:16:01 - 0:16:03 = 0:00:02
redbelly:1/1048576 0:16:17 - 0:16:20 = 0:00:03
redbelly:1/1048576 0:16:31 - 0:16:40 = 0:00:09
redbelly:0/1048576 0:16:46 - 2:38:27 = 2:21:41
redbelly:0/1048576 2:38:28 - 5:04:48 = 2:26:20 => 4:48:17
anaconda:1/1048576 0:14:51 - 0:14:52 = 0:00:01
anaconda:1/1048576 0:15:07 - 0:15:47 = 0:00:40 => 0:00:41
###
Just thought I would share these differences... in case it meant
something to someone.
##########
I am just looking for general info about how amadmin and amplot can
be used. (like wrapping them in a larger script).
One thing I noticed with amplot was the fact that the X window never
showed on the screen... I suppose more experimentation is in order...
:)
Also, has anyone written analysis scripts that evaluate multiple amdump runs?
thank you...
dk
PS: and before anyone asks, my mail client seems to be broken.. sorry
for the long lines.
|
|
|
