I am running the following perl script called with 0 as the argument (we have a lot of db2 disks so I need to break the space monitor into several components):
use threads;
use threads::shared;
#File system stats output: IO%
@stdOut1 = split("\n", `df |grep -i db2`);
$fsName = "";
$i = $ARGV[0];
$max = $ARGV[0]+10;
$used = "";
while ($i<$max){
@stats = split(" ", $stdOut1[$i]);
$fsName = $stats[6];
$fsName =~ tr/\//-/;
$used = substr($stats[3],0,-1);
print "Message.$fsName: $diskName has $used \% used space\n";
print "Statistic.$fsName: $used\n";
$i++;
}
exit 0;
When I runn it on the server it returns this:
[user_name@[server_name][max-db2-dev][/tmp]perl test1.pl
Message.-db2-encdvi-data01: -db2-encdvi-data01 has 28 % used space
Statistic.-db2-encdvi-data01: 28
Message.-db2-encdvi-data02: -db2-encdvi-data02 has 28 % used space
Statistic.-db2-encdvi-data02: 28
Message.-db2-encdvi-backup: -db2-encdvi-backup has 1 % used space
Statistic.-db2-encdvi-backup: 1
Message.-db2-encdvi-systmp01: -db2-encdvi-systmp01 has 1 % used space
Statistic.-db2-encdvi-systmp01: 1
Message.-db2-encdvi-systmp02: -db2-encdvi-systmp02 has 1 % used space
Statistic.-db2-encdvi-systmp02: 1
Message.-db2-encdvi-dbhome: -db2-encdvi-dbhome has 4 % used space
Statistic.-db2-encdvi-dbhome: 4
Message.-db2-encdvi-logs: -db2-encdvi-logs has 7 % used space
Statistic.-db2-encdvi-logs: 7
Message.-db2-encdvi-catalog: -db2-encdvi-catalog has 56 % used space
Statistic.-db2-encdvi-catalog: 56
Message.-db2-encdvi-foglight: -db2-encdvi-foglight has 1 % used space
Statistic.-db2-encdvi-foglight: 1
Message.-home-db2-encdvi: -home-db2-encdvi has 9 % used space
Statistic.-home-db2-encdvi: 9
[user_name@[server_name][max-db2-dev][/tmp]
When I run it from the Orion server I get "Can't identify dynamic column definitions from script output. Please, check if script output has properly formatted unique identifiers." (and BTW...the link is teats on a Bull useless)
If I change the "$fsName" to read the incementer ($i) I get a useless but valid return on the server:
Message.: -db2-encdvi-data01 28 % used space
Statistic.: 28
Message.1: -db2-encdvi-data02 28 % used space
Statistic.1: 28
Message.2: -db2-encdvi-backup 1 % used space
Statistic.2: 1
Message.3: -db2-encdvi-systmp01 1 % used space
Statistic.3: 1
Message.4: -db2-encdvi-systmp02 1 % used space
Statistic.4: 1
Message.5: -db2-encdvi-dbhome 4 % used space
Statistic.5: 4
Message.6: -db2-encdvi-logs 7 % used space
Statistic.6: 7
Message.7: -db2-encdvi-catalog 56 % used space
Statistic.7: 56
Message.8: -db2-encdvi-foglight 1 % used space
Statistic.8: 1
Message.9: -home-db2-encdvi 9 % used space
Statistic.9: 9
This script format works on the "standard" mountpoints; /tmp, /home, etc., but not on our DB2 maount points. Am I hitting an undocumented limit on metric names?