Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

Legacy SQL Server 2008 Reporting Services

This SAM template uses Windows performance counters to assess the status and performance of Microsoft SQL Server 2008 Reporting Services.

Prerequisites:

WMI access to the target server.

Credentials:

Windows Administrator on the target server.

Component monitors

Click here for an overview about SAM application monitor templates and component monitors. SAM API Poller templates are also available.

MSRS Windows Service: Active Sessions

This monitor returns number of active sessions. This counter provides a cumulative count of all browser sessions generated from report executions, whether they are still active or not. The counter is decremented as session records are removed. By default, sessions are removed after ten minutes of no activity.

MSRS Windows Service: Cache Flushes/Sec

This monitor returns number of cache flushes per second.

MSRS Windows Service: Cache Hits/Sec

This monitor returns number of requests per second for cached reports. These are requests for re-rendered reports, not requests for reports processed directly from the cache.

MSRS Windows Service: Cache Misses/Sec

This monitor returns the number of requests per second that failed to return a report from the cache. Use this counter to find out whether the resources used for caching (disk or memory) are sufficient.

MSRS Windows Service: Delivers/Sec

This monitor returns the number of report deliveries, per second, from any delivery extension.

MSRS Windows Service: Events/Sec

This monitor returns the number of events processed per second. Events that are monitored include SnapshotUpdated and TimedSubscription.

MSRS Windows Service: Memory Cache Hits/Sec

This monitor returns the number of times per second that reports are retrieved from the in-memory cache. In-memory cache is a part of the cache that stores reports in CPU memory. When in-memory cache is used, the report server does not query SQL Server for cached content.

MSRS Windows Service: Memory Cache Miss/Sec

This monitor returns the number of times per second that reports could not be retrieved from the in-memory cache.

MSRS Windows Service: Reports Executed/Sec

This monitor returns the number of successful report executions per second. This counter provides statistics about report volume. Use this counter with Request/Sec to compare report execution to report requests that can be returned from cache.

MSRS Windows Service: Total Processing Failures

This monitor returns the number of errors in report server web service request processing.
Note: This counter has the Count statistic as difference option enabled and will show the statistical difference from the last polling cycle.

MSRS Windows Service: Total Rejected Threads

This monitor returns the total number of threads rejected for asynchronous processing, and subsequently handled as synchronous processes in the same thread. 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.
Note: This counter has the Count statistic as difference option enabled and will show the statistical difference from the last polling cycle.

Report Server: Active Connections

This monitor returns the number of connections currently active on the server.

Report Server: Bytes Received/sec

This monitor returns the number of bytes received per second by the server. This counter is updated only when a transfer is complete. This means that the counter remains at 0 and then the value increases after a transfer is complete.

Report Server: Bytes Sent/sec

This monitor returns the number of bytes sent per second from the server. This counter is updated only when a transfer is complete. This means that the counter remains at 0 and then the value increases after a transfer is complete.

Report Server: Errors/sec

This monitor returns 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.

Report Server: Logon Attempts/sec

This monitor returns the rate of logon attempts.

Report Server: Logon Successes/sec

This monitor returns the rate of successful logons.

Report Server: Memory Pressure State

This monitor returns the 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

Report Server: Memory Shrink Amount

This monitor returns the number of bytes that the server requested to shrink the memory in use.

Report Server: Memory Shrink Notifications/sec

This monitor returns 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.

Report Server: Requests Executing

This monitor returns the number of requests that are currently processing.

Report Server: Requests/sec

This monitor returns the number of requests that are processed per second. This value represents the current throughput of the application.

Report Server: Tasks Queued

This monitor returns 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 does not include the number of tasks that are currently running.

Service: SQL Server Reporting Services

This monitor returns CPU and memory usage of SQL Server Reporting Services. This service manages, executes, renders, schedules and delivers reports.

Report Server TCP Port

This component monitor tests the ability of a Report Server to accept incoming sessions. By default, it monitors TCP port 80.