User1771714573 postedHi Parkiis,
In the iis server farm interface, you can see health test and monitoring and management.
Health test, you can schedule explicit health checks and/or rely on live traffic tests. Live traffic testing watches for errors with the live traffic. If it sees what you define as a failure it marks that server as unhealthy. With explicit URL testing you ask ARR to send a request to the web farm members with specific time intervals and inspect the response. The test request will be sent to each machine in the farm. ARR will mark the server as unhealthy after the very first bad response.
ARR exposes runtime statistics on the Monitoring and Management page. You can see the real-time statistics. While this works well for one instance of ARR.
The above two can monitor and find out the problematic servers in the server farm. But if you want to find the problematic server during a certain request, it is recommended that you use fail request tracing.
In the FREB log generated after enabling, the header and information will show you where the request has the problem and which server it entered. Then you can determine whether it is the ARR or the server problem, and then check on the server.
It is strongly recommended that you read the relevant documents, which describe in detail how to use fail request tracing to troubleshoot the server farm.
Best regards,
Brucz
