Overview
There might be situations where the IP address that you see in the browser snapshots for incoming requests is not what you expect.
This document mentions the precedence of how the IP address is resolved for an incoming request. However, sometimes there may be mis-configurations at the network device level, which may make it hard to debug the issue.
Debugging IP address resolution
To debug the IP address resolution, add the following logger to the EUM server
(<eum_install_dir>/eum-processor/bin/logback.xml)
<logger name="com.appdynamics.eumcloud.processor.collector.ABeacon"
level="TRACE" additivity="false">
<appender-ref ref="FILE"/>
</logger>
A log appears like the following: In the EUM log (eum-processor.log file)
06 Nov 2015 02:24:04.978 -0800 Beacon to Record Converter-1 AD.ABeacon TRACE
HEADER_AD_X_FORWARDED_FOR: null
06 Nov 2015 02:24:04.984 -0800 Beacon to Record Converter-1 AD.ABeacon TRACE
HEADER_X_FORWARDED_FOR: 14.102.224.6
This tells you the exact source of the IP address that is being resolved (HTTP request, X_FORWARDED_FOR header, AD_X_FORWARDED_FOR header, etc).
