Problem with ClientIP Business Transaction since v6.1 upgrade

Question

Question by Joell C. · Jun 03, 2015 at 09:11 PM ·

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 prior to upgrade.JPG

ClientIP current.JPG

ClientIP Business transaction.JPG

Any thoughts or input on why this isn't working would be appreciated.

Thanks!

Joell

0

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 1 · 2015-06-26T18:05:57Z

Answer by Joell C. · Jun 26, 2015 at 06:05 PM

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

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 2 · 2015-06-08T23:01:53Z

Answer by Joell C. · Jun 08, 2015 at 11:01 PM

Thanks! I'm getting the Header name from the developer and then I just add it above these? Is that correct?

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 3 · 2015-06-04T10:39:39Z

Answer by SU C. · Jun 04, 2015 at 10:39 AM

Hi Joell,

You can try to add HTTP request header.

0 Show 1 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Reinhard W. · Jun 09, 2015 at 05:05 AM 0

Share

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 (smile)

Reinhard

Problem with ClientIP Business Transaction since v6.1 upgrade

3 Replies

How to get started

NAM 2019 SP5 is available

LIVE WEBINAR

Follow this Question

Forum Tags