IIS-源IP日志分析
我有 2 个网络服务器托管着大约 70 个网站。负载平衡是通过 Radware App Director 完成的。我的日志分析有问题，因为对 70 个站点的所有请求都是通过 App Director 路由的，IIS 日志文件中的源 IP 显示 APP Director 的 IP，而不是请求的实际源 IP被发送到网站。因此，在解决特定站点的问题时，我在跟踪原始源 IP 方面遇到了很多问题。是否有任何解决方案来解决此日志异常，以便 IIS 日志中的源 IP 反映实际源的 IP，而不是 App Director 的 IP？
I'm having 2 web-servers hosting around 70 websites. The load balancing is done through Radware App Director. I have an issue with the logs Analysis, since all the requests to the 70 odd sites is routed through App Director, the source IP in the IIS Log files shows the IP of APP Director , rather than the IP of actual source from where the request is sent to the web site. So I face a hell lot of problems to track the originating source IP when resolving issues with the specific sites. Is there any solution to resolve this Log anomaly so that the source IP in the IIS Log reflects the IP of the actual source rather than the App Director's IP?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这可以通过捕获并传递 X-Forwarded-For 来实现。如果您进行搜索，我想您会找到您正在寻找的答案。我们通过 F5 BigIP 负载均衡器进行负载均衡，并且遇到了同样的问题。 F5 上有一个选项可以“启用 X-Forward-For”，IIS 服务器上有一个 ISAPI，可以将其解释为 clientIP 并将其写入 IIS 日志中。
This is possible to do by capturing and passing through X-Forwarded-For. If you do a search for that I imagine you will find the answer you are looking for. We are load balancing through an F5 BigIP Load balancer and had thesame issue. There is an option on the F5 to "enable X-Forward-For" and an ISAPI on the IIS servers to interpret and write it as the clientIP in the IIS logs.