Answer by Ted F. ·
Hi Dave,
You need to configure the F5 to pass a header through that we can use for the IP Address. F5's are typically configured to block these headers by default. It can be any of the headers you have listed (e.g True-Client-IP, X-Forwarded-For) - but, it can actually be any header as you can add headers to the list that we use in the dynaTrace Server Settings->Geographical Locations screen. So, yes, you can control what header dynaTrace gets the IP from - but, the key is get the F5 to pass it through so dynaTrace can see it.
===ted
Answer by David D. ·
When using UEM the visits dashlet shows the same ip for all visitors. This is because of the F5 switch. The IP that is displayed is the F5 IP. However, we would like to see the true IP addresses of the visitors?
The documentation explains where the value comes from but not how to get it. The document I am referencing is Geographical Location Configuration. It says that in cases of load balancers (I assume that includes F5) the IP is determined from the following headers:
1.http-requestheader field "rproxy_remote_address": this header is preliminary and it is likely to be changed or removed in future versions
2.http-requestheader field "True-Client-IP"
3.http-requestheader field "X-Client-Ip"
4.http-requestheader field "X-Forwarded-For"
5.http-requestheader field "X-Http-Client-Ip"
6.ip-address of requester
From this documentation it sounds like this should be working. But it is not. Is there something I need to turn on to ensure it looks at the header values shown above? Do I have options to control what header field I get the IP value from?
Thanks,
David
JANUARY 15, 3:00 PM GMT / 10:00 AM ET