Forum Discussion

Gibbo_15575's avatar
Gibbo_15575
Icon for Nimbostratus rankNimbostratus
Oct 03, 2012

Analytics

I've got the Analytics enabled (nominal) and wanted to see if there was a way to see which source ips of the users are/have been associated to which pool member in a virtual server? (I.e. in a simply example with 2 nodes in a pool: user 1 is mapped to pool member 1, user 2 is mapped to pool member 2, user 3 is mapped to pool member 1, user 4 is mapped to pool member 2)

 

I can see in transactions you can see pool members or client ip addresses, but not easily which client is going to a particular pool member. Wasn't sure if this was possible in the analytics section? Has anyone setup this sort of information? I've had a dig around and under the Statistics >> Module Statistics >> Local Traffic, where you can select Pools as the stat type, it does show bits in/out, packets, connections to each pool member etc, but I was hoping to find a view preferably in real time that would show what source ips are mapped to which pool member in case for some reason we needed to take the pool member out the pool we'd know how many (and who) would be affected by this (we have sticky cookie persistence so users are tied to a particular web pool member).

 

management
monitoring

1 Reply

Sort By
  • What_Lies_Bene1's avatar
    What_Lies_Bene1
    Icon for Cirrostratus rankCirrostratus
    Oct 09, 2013

    I don't think Analytics or even an iRule is going to help you here. However, if ID'ing the actual users isn't required I'd suggest finding a statistics for layer four sessions (rather than TCP connections); this should give you an accurate figure assuming you're not using WA or doing anything interesting to increase performance. I'll get back to you shortly after taking a look at my VE.

     

    Update: OK, I've not got AVR provisioned so sticking to standard statistics your best bet appears to be: Statistics > Module Statistics > Local Traffic > Persistence Records. You should then be able to filter on a particular Pool Member as required. Obviously each record represents one user.

     

    Further update: Remembered you're using Cookie Persistence so this probably is no good. Standby...