Monitor instance status checking

On second thoughts unfortunatly that still doesn't get what I need.

Here's an example output for a test pool:

 
 Pool gj_pool { 
   Member   : 192.168.123.123:1234 
     Template : http 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_DOWN 
                Enabled State :Enabled 
   Member   : 192.168.222.222:80 
     Template : gj_specific_port_specific_addr 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_DOWN 
                Enabled State :Enabled 
     Template : gj_specific_port_specific_addr 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_DOWN 
                Enabled State :Enabled 
     Template : gj_specific_port_specific_addr 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_DOWN 
                Enabled State :Enabled 
   Member   : 192.168.230.133:80 
     Template : http 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_UP 
                Enabled State :Enabled 
   Member   : 192.168.230.161:80 
     Template : http 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_UP 
                Enabled State :Enabled 
 } 
 

There are 3 nodes in this pool, namely 192.168.230.133:80, 192.168.230.161:80, and 192.168.123.123:1234. The pool has the 'http' and 'gj_specific_port_specific_addr' monitors associated with it.

The 'gj_specific_port_specific_addr' as its name implies has a specified destination and port for the monitor and this is not one of the monitored nodes.

I need the output to be like this:

 
 Pool gj_pool { 
   Member   : 192.168.123.123:1234 
     Template : http 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_DOWN 
                Enabled State :Enabled 
     Template : gj_specific_port_specific_addr 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_DOWN 
                Enabled State :Enabled 
   Member   : 192.168.230.133:80 
     Template : http 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_UP 
                Enabled State :Enabled 
     Template : gj_specific_port_specific_addr 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_DOWN 
                Enabled State :Enabled 
   Member   : 192.168.230.161:80 
     Template : http 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_UP 
                Enabled State :Enabled 
     Template : gj_specific_port_specific_addr 
                Address Type  : ATYPE_EXPLICIT_ADDRESS_EXPLICIT_PORT 
                Instance State: INSTANCE_STATE_DOWN 
                Enabled State :Enabled 
 } 
 

Thus mirroring the output you get when you click a pool member in the 'members' tab in the 'pools' section in the web interface.

Is the output from LocalLB::Pool::get_monitor_instance() sorted in the same order as LocalLB::Pool::get_member()? I think when I tested it it isn't guarenteed to match but I could be going wrong.