Initial Configuration


The Management Pack automatically discovers instances of the SQL Reporting Services running within the Operations Manager 2007 management group, and deploys the Reporting Services monitoring agent to those servers (aka Monitored Systems). Once the agents have been deployed, they automatically begin monitoring SQL Reporting Services applications for performance and exception issues.

The agent monitors for problems in the .NET elements of SQL Reporting Services applications, as indicated on the diagram by .  With the AVIcode .NET MP also installed, you can monitor .NET Windows Services, Web Services and COM+ components that your SQL Reporting Services application communicates with, or any other ASP.NET application hosted under IIS.

SQL Reporting Services 2005 Monitoring

SQL Reporting Services 2008 Monitoring


The management pack performs automated discovery and configuration of monitoring for all Reporting Services components, including the Reporting Service interface and Report web service.

.NET Enterprise Agent Deployment Group

The members of the .NET Enterprise Agent Deployment Group were selected when the Management Pack was installed. To modify the group membership:

To add Explicit members to the group, select the Explicit Members tab.

To add Dynamic members to the group, select the Excluded  Members tab.

To Exclude members from the group, select the Dynamic Members tab.

Forcing Discovery

If discovery Reporting Services components fails, it will normally take 4 hours before a new discovery attempt takes place unless discovery is forced.

Forcing Discovery Method #1

This method is not recommended for production servers because it requires having to restart the OpsMgr main windows service.

Forcing Discovery Method #2

This method requires changing the discovery interval to 1 minute (for example), waiting for the next discovery, and then changing the discovery interval back to 6 hours. This method is much longer, but no any harmful operation is done during it.

Initial Settings

Application health is measured by user-specified performance and exception thresholds that are configured during the monitoring activation process. By default, the Management Pack monitors SQL Reporting Services applications for:

The SLA threshold is set to a very high value (1000000) out of the box to avoid the possibility of generating too many events when monitoring is automatically started. Read the following sections for instructions to fine tune data collection.


Changing the Settings

The agents may be configured via the Tasks in the Operations Console.

If the Tasks are not visible, select 'View''Actions' in the Operations Console.

Selecting the Target

To select an object to apply an action to:

Available Tasks

Reporting Services Tasks

Start SQL Reporting Services Service

This task is the equivalent of starting SQL Server Reporting Services (ReportingServicesService.exe) on the target machine through the Windows Services snap-in.

Stop SQL Reporting Services Service

This task is the equivalent of stopping SQL Server Reporting Services (ReportingServicesService.exe) on the target machine through the Windows Services snap-in.

Reporting Server and Reporting Server Interface Tasks

Enable [Disable] Exception Diagnostic Data

This task enables/disables collecting exception diagnostic data in the monitored application. It adds All Namespaces into the list of monitored namespaces in order to collect functional parameters and member variables for custom namespaces in the exception event.

Enable [Disable] Performance Diagnostic Data

This task adds All Namespaces to collected information in the monitored application (or disables collecting performance diagnostic data in the monitored application).  This option will cause the agent to start monitoring all functions except namespaces, classes and functions that are explicitly excluded from monitoring. 

The '[All Namespaces]' item should be used judiciously as it will increase the amount of data collected.

Pause [Resume] Monitoring Application

This option disables [enables] monitoring.

This option starts/stops monitoring for a specific web site.

Set Alerting Threshold

An SLA threshold is used by the operations monitoring agent to define if an event needs to be reported. The operations monitor detects all requests that exceed this threshold and reports them.  If the execution time for a request exceeds the alerting threshold, then the agent collects information about the request and reports it, otherwise the agent disposes the event data.

Set Sensitivity Threshold

The threshold for the execution time of a call to external resources (such as SQL queries or web service calls) is called the 'Sensitivity Threshold'. The sensitivity threshold for a resource call should never exceed the alerting threshold of the page or function it was called from. In a staging or test environment, setting the sensitivity threshold to zero will allow Intercept to report performance information on all resource calls, including those that took no time. In a production environment however, you should reduce overhead by eliminating the reporting of resource calls that took a negligible amount of time. This will help to eliminate extraneous information, which is of no interest in the alert.

Advanced Configuration

Additional configuration options are available through the Intercept Management Console and through the agent configuration files. Details are available in the "Intercept Studio User Manual" .

Last update: Thursday, December 09, 2010 02:05:37 PM