Problem with ClientIP Business Transaction since v6.1 upgrade
Prior to upgrading dT to v6.1 (we upgraded from v5.6), we had a Business Transaction called ACES Requests by ClientIP that showed all our "work at home" claims processors by IP address so we could troubleshoot slow responses. I don't know how the Business Transaction was set up for sure (completed in a Coaching Session with someone else working with the Coach), so if someone could help me with how to locate where the IP address range would be set up, that would help first. But second, would there be some configuration that would need to be done in windows server that could be accounting for the change? The way the Business Transaction is working now, it's lumping all the activity under the IP address for our Virtual Netscaler device that handles load balancing.
ClientIP Business transaction.JPG
Any thoughts or input on why this isn't working would be appreciated.
Thanks!
Joell
Hi Joell,
You can try to add HTTP request header.
Gareth,
I think that might not work in Joell's BT as it's a serverside PurePath BT and not a UEM BT. Joell, I guess your Netscaler replaces the real Client IP header on the webrequest with it's own IP. You will need to
a) capture the according header on the webrequest which has the real Client IP (maybe X-Forwarded-For is a good guess)
b) create a custom webrequest header measure in your splitting that uses this header
Apart from that I think it's not a good idea to split a BT by a attribute that can have a very large amount of options like IP's, but in your case as you are not storing the data in performance warehouse you should be fine for a live session. Just remember to keep that setting off 
Reinhard
Thanks! I'm getting the Header name from the developer and then I just add it above these? Is that correct?
Thanks for the input, with a little dT assistance we got this working again. We had to turn on all Response Headers for the Tier, then go look at the details for one of the PurePaths. With all the information on, we were able to see the IP address in the client-ip Request Header. We then left only the client-ip active in the Tier and also added it to the Geographical Location and we're back to seeing all our application traffic for this application broke out by IP Address.
Joell
