Expected behavior
When unmasking Client IP in Log Analytics (https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net), the Client IP should be the public IP of the end-user.
Actual behavior
When unmasking Client IP in Log Analytics (https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net), the IP appearing is the server outbound IP (and not the end user Public IP).
ENVIRONMENT
Web Server: JBoss Wildfly 17.0.1 Standalone
Web Application: Sample Maven Web Application Hello World
To Reproduce
Steps to reproduce the behavior:
Deploy applicationinsights-agent-3.0.2.jar and the web application on a Wildfly Standalone web server. The agent 3.0.2 send server telemetry to app insight, but the client IP is the outbound ip of the server. There is also no AI tracking cookie attached to the responses, is that expected ?
Expected behavior
When unmasking Client IP in Log Analytics (https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net), the Client IP should be the public IP of the end-user.
Actual behavior
When unmasking Client IP in Log Analytics (https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net), the IP appearing is the server outbound IP (and not the end user Public IP).
ENVIRONMENT
Web Server: JBoss Wildfly 17.0.1 Standalone
Web Application: Sample Maven Web Application Hello World
To Reproduce
Steps to reproduce the behavior:
Deploy applicationinsights-agent-3.0.2.jar and the web application on a Wildfly Standalone web server. The agent 3.0.2 send server telemetry to app insight, but the client IP is the outbound ip of the server. There is also no AI tracking cookie attached to the responses, is that expected ?