DX Infrastructure Management

Nice post and I wish I had this in place yesterday.

In hopes of sharing a little of my learning today, I had a hub that had been offline for an extended period of time and some time in the last 48 hours, someone restarted the hub and it started working again. Had about 60 million messages queued up (had been offline for a long time) which was completely swampping my nas.

Not having this tool in place, I crafted a quick and dirty one liner that provides a way of identifying queues with the highest rate of change in content:

/opt/nimsoft/bin/pu -u administrator -p XXXXXXXX hub list_subscribers | 
     awk ' BEGIN { 
                         q=""; c=0; s=0; g=0; 
                         while (getline < "queuecount.txt" > 0 ) { 
                              split($0, ft, " "); 
                              a[ft[1]]=ft[2];
                         } 
                         close("queuecount.txt") 
                    } 
               /[[:space:]]+[[:digit:]]+[[:space:]]+PDS_PDS/ && match(q, /^All_/) && g==1 { 
                    print "Queue [", q, "] Count [", c, "] Diff [", c - a[q], "]"; 
                    print q, c > "queuecount.txt" ;  
                    q=""; c=0; s=0; g=0; 
               } 
               /[[:space:]]+name[[:space:]]+/ {
                    q=$4
               } 
               /[[:space:]]+count[[:space:]]+/ {
                    c=$4
               } 
               /[[:space:]]+connected[[:space:]]+/ { 
                    g=1 
               } 
          ' | 
          sort -k 11n

Run this on the hub with the GET queues and it will quickly calculate a baseline. Run it a second time and it provides a delta count and sorts the list so that the highest rate queues are listed at the bottom of the list.

All the queues I'm concerned about begin with "ALL_" which the function match(q, /^All_/) filters for. You could put your own pattern in there or remove it.

This creates a file queuecount.txt which holds the counts from the previous run.

This gets read in the BEGIN section and then used to calculate the difference when printed.

Some nifty awk usage that hopefully is helpful for someone else.

Hi Thomas,

Feel free to modify/optimize the posted code. (and post it back if possible)

Regards, Luc

Hi Chris,

It could be cool to open this script to every one on a git. I already spotted a lot of things to optimize (performance and readability). 

Things like : 

if cond then

    -- do the job

else 

   -- oh no

end 

can be rewritten like this : 

if cond == false then

    -- oh no

    return;

end

-- do the job 

That useful to avoid tab **** when you have three or four conditions.

Best Regards,

Thomas