SharePoint Request Management Test

Request Manager is a functionality in SharePoint Server that enables administrators to manage incoming requests and determine how SharePoint Server routes these requests.

Request Manager uses configured rules to perform the following tasks when it encounters requests:

  • Deny potentially harmful requests from entering a SharePoint farm.

  • Route good requests to an available server.

  • Manually optimize performance.

There are three logical components of the request manager:

  • Throttling (Limit request) and Routing (route request)

  • Prioritization (identify the group of servers to handle request)

  • Load balancing (Identify the server to handle request).

Using the SharePoint Request Management test, you can measure the effectiveness of the request management rules that have been configured. Alerts are sent out if the test captures request failures and network/processing latencies, as these are the anomalies that the Request Manager strives to avert. The occurrence of such anomalies are signs that the request management rules need fine-tuning.

Target of the test : A Microsoft SharePoint Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results each for the Microsoft SharePoint server that is being monitored

Configurable parameters for the test
Parameters Description

Test period

This indicates how often should the test be executed.


The host for which the test is to be configured.


The port at which the host server listens.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Unfinished routed requests

Indicates the number of requests being routed.



Total number of connection endpoints

Indicates the total number of connection endpoints.



Last ping latency

Indicates the time taken to respond to the last ping.


If the value of this measure is consistently high, it indicates a latent network connection.

Failed requests per second

Indicates the number of requests that failed.


Ideally, the value of this measure should be 0 or low. A high value indicates that one/more requests to the SharePoint farm failed.

Typically, a request may fail if the SharePoint server processing that request fails. Request Manager can send all requests of a specific type, for example, Search, User Profiles, or Office Online, to specific computers. When a computer is failing or slow, Request Manager can locate the problem, and route requests to available/faster servers in the farm.

Throttled requests per second

Indicates the number of requests that are throttled per second.


A Throttling Rule is the definition of the criteria to evaluate before refusing requests which match the criteria.

The Request Manager evaluates every request against the throttling rules that are configured, and does not send requests that fulfill one/more throttling rules to any server in the SharePoint farm that it manages.

A high value for this measure means that many requests have been ignored. To reduce throttling, you may want to tweak the throttling rules.

Current requests per second

Indicates the number of requests processed per second.



Reused connections per second

Indicates the number of connections reused.



Total number of connections

Indicates the total number of connections to the SharePoint farm managed by the Request Manager.,



Average processing time

Indicates the average time taken by the Request Manager to process requests.


An unusually high value or a steady rise in the value of this measure could indicate processing latencies.

To avoid such latencies, you may want to configure the Request Manager to route requests to front-end web servers that have better performance.

Requests received

Indicates the number of requests received per second on Excel Calculation Services.



Active requests

Indicates the number of requests being actively processed on Excel Calculation Services.