SQL SSRS Threads Test
Monitoring thread usage is the ideal way to gauge the workload of the report server. Each data source is processed on one thread. If the volume of threads exceeds capacity, threads are rejected for asynchronous processing, and are then processed in a serial manner.If the server rejects many threads, it is often indicative of an overload condition. To detect such conditions, use the SQL SSRS Threads test.
This test reports the rate of rejected threads, and thus indicates if the report server is handling more load than it can.
Target of the test : A Microsoft SQL Server Reporting Services server
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the report server being monitored
| Parameters | Description |
|---|---|
|
Test period |
How often should the test be executed |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port at which the specified Host listens. |
|
Instance |
The name of a specific SQL Report server instance to be monitored. The default value of this parameter is “default”. However, if the Microsoft SQL Server hosting the SQL Reporting Server database uses named instances, then do the following:
|
|
Is Passive |
If the value chosen is Yes, then the Microsoft SQL server (hosting the SQL report server database) under consideration is a passive server in a SQL cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable’ by the agent if the server is not up. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Rejected threads |
Indicates the rate at which threads are rejected for asynchronous processing, and subsequently handled as a synchronous process in the same thread during the measure period. |
Errors/Sec |
Under moderate or heavy load, this measure steadily increases. High values of this measure indicates that the report service is running in high load. |
