It looks like our load-balancer puts the actual client-ip into a specific header field (e.g. x-client-ip). Right now UEM is mapping all requests as initiating from the local network as its the IP of the load balancer. Is there some ability to configure UEM to recognize a different attribute as the true client IP?
Answer by Andreas G. · Dec 14, 2011 at 08:43 AM
Hi
UEM actually looks at different HTTP Headers to determine the IP Address - this is documentented @ User Experience Management#GeoLocation
UEM basically looks at the following HTTP Headers in the following order:
1.http-requestheader field "True-Client-IP"
2.http-requestheader field "X-Client-Ip"
3.http-requestheader field "X-Forwarded-For"
4.http-requestheader field "X-Http-Client-Ip"
5.ip-address of requester
In your case it's likely that the header "True-Client-IP" is set by your load-balancer with the IP address of the Load-Balancer. Can you verify that?
If thats the case - you can either change that value to the original client-ip-address or just omit this header so that UEM will just pick up X-Client-Ip
Hope this helps
Answer by Coburn W. · Jan 10, 2012 at 06:37 PM
Hi Andreas,
Thanks for the reply. As it turns out we use the zeus load balancer from ZWS and they put the client IP in the following header:
x-cluster-client-ip:
70.61.88.178
x-cluster-client-ip
Is there a capability with UEM to provide the header to use for gelocation in a declarative fashion?
Hi
We are implementing this feature right now so that you can configure the HTTP Header to use for client ip resolving. Its planned to be released with the next dynaTrace minor release.
Right now - with dynaTrace 4.1 - you have to find a workaround in order to make it work. Is there any chance you can change your load balancer to use one of the mentioned HTTP headers?
Andi
Hi Andreas,
I am getting pushback from my operations team to fiddle with anything at the load-balancer level in production. I am planning to move to 4.1 in production in the coming weeks. What is your timeline to have configurable values on for this header baked into the product? We just purchased a somewhat large UEM license and it would be great to show our stakeholders the world map view (right now it looks sort of silly as all traffic is from our datacenter ;-) with the default client-ip).
Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!
Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!
Would you like to have an early taste of what we have cooked up for 2019? We would love to hear your feedback and improve some of the new features. Check NAM 2019 Beta release notes.
Sign up today!