This article describes performance counters for the ReportServer:Service and ReportServerSharePoint:Service performance objects that are part of a SQL Server 2012 (11.x) deployment.
Note
The performance objects are used to monitor events on the local report server. If you're running a report server in a scale-out deployment, the counts apply to the current server and not the scale-out deployment as a whole.
The performance objects are available in the Windows Performance Monitor (Perfmon.exe). For more information, see the Windows documentation. Runtime Profiling.
The ReportServer:Service performance object includes a collection of counters to track HTTP-related events and memory-related events for a report server instance. This performance object appears one time for each Reporting Services instance on the computer, and you can add or remove counters from the performance object for each instance. Counters for the default instance appear in the format ReportServer:Service. Counters for named instances appear in the format ReportServer$\<instance_name>:Service.
The ReportServer:Service performance object was new in SQL Server 2008 (10.0.x) Reporting Services, and it provides a subset of counters that were included with Internet Information Services (IIS) and ASP.NET in previous versions of Reporting Services. These new counters are specific to Reporting Services, and they track HTTP-related events for the report server, such as requests, connections, and sign in attempts. Additionally, this performance object includes counters to track memory management events.
The following table lists the counters that are included in the ReportServer:Service performance object.
The following Windows PowerShell script returns the list of performance counters for the CounterSetName:
The number of connections currently active on the server.
Bytes Received Total
The number of bytes received by the server. This counter counts the raw bytes received in total by both Report Manager and the report server.
Bytes Received/sec
The number of bytes received per second by the server. This counter is updated only when a transfer is completed. This result means that the counter remains at 0 and then the value increases after a transfer is complete.
Bytes Sent Total
The number of bytes sent from the server. This counter counts the raw bytes sent in total by both Report Manager and the report server.
Bytes Sent/sec
The number of bytes sent per second from the server. This counter is updated only when a transfer is completed. This result means that the counter remains at 0 and then the value increases after a transfer is complete.
Errors Total
The total number of errors that occur during the processing of HTTP requests. These errors include HTTP status codes in the 400s and 500s.
Errors/sec
The total number of errors that occur per second during the processing of HTTP requests. These errors include HTTP status codes in the 400s and 500s.
Logon Attempts Total
The number of sign-in attempts made from RSWindows authentication types. RSWindows authentication types include RSWindowsNegotiate, RSWindowsNTLM, RSWindowsKerberos, and RSWindowsBasic. The value zero (0) represents Custom authentication.
Logon Attempts/sec
The rate of sign-in attempts.
Logon Successes Total
The number of successful logons for RSWindows authentication types. RSWindows authentication types include RSWindowsNegotiate, RSWindowsNTLM, RSWindowsKerberos, and RSWindowsBasic. The value zero (0) represents Custom authentication.
Logon Successes/sec
The rate of successful logons.
Memory Pressure State
One of the following numbers, from 1-5, which indicates the current memory state of the server:
1: No pressure
2: Low pressure
3: Medium pressure
4: High pressure
5: Exceeded pressure
Memory Shrink Amount
The number of bytes that the server requested to shrink the memory in use.
Memory Shrink Notifications/sec
The number of notifications that the server issued in the last second to shrink the memory in use. This value indicates how often the server experiences memory pressure.
Requests Disconnected
The number of requests that are disconnected because of a communication failure.
Requests Executing
The number of requests that are currently processing.
Requests Not Authorized
The number of requests that fail with an HTTP 401 status code.
Requests Rejected
The total number of requests that weren't processed because of insufficient server resources. This counter represents the number of requests that return an HTTP 503 status code, which indicates that the server is too busy.
Requests Total
The total number of requests that the report server service received since startup. This counter counts requests that are sent to Report Manager and requests that are sent from Report Manager to the report server.
Requests/sec
The number of requests that are processed per second. This value represents the current throughput of the application.
Tasks Queued
The number of tasks that are waiting for a thread to become available for processing. Each request made to the report server corresponds to one or more tasks. This counter represents only the number of tasks that are ready for processing; it doesn't include the number of tasks that are currently running.
Learn to use a range of Windows Server tools to monitor the operating system and applications on a server computer. You'll also learn to configure your system to optimize efficiency and to troubleshoot problems.