Default Parameters for SSRSRespTest

This test auto-discovers report server users, and for each user, tracks the running time of every report executed by that user. If the execution time of a report exceeds an acceptable, userconfigured running duration, then such a report will be counted as a slow report. The test then reports the count of slow reports per user, and the maximum time spent by every user at different stages of report processing. This way, the test points administrators to the probable cause of the processing bottleneck. Detailed diagnostics provided by the test reveal the exact reports that are slow, and points administrators to the precise reason for their slowness.

This page depicts the default parameters that need to be configured for the SSRSRespTest test.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• Specify the name of a specific SQL Report server instance that is to be monitored in the INSTANCE text box. 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:

  • Configure the INSTANCE parameter with the name of the SQL Server instance that hosts the SQL Report Server database.

  • Do not change the default value of the PORT parameter.

• If the value for the ISPASSIVE parameter is chosen as 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.

• In some Windows networks, NTLM (NT LAN Manager) may be enabled. NTLM is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. NTLM version 2 NTLMv2 was concocted to address the security issues present in NTLM. By default, the IS NTLMv2 flag is set to No, indicating that NTLMv2 is not enabled by default on the target Microsoft SQL server hosting the SSIS database. Set this flag to Yes if NTLMv2 is enabled on that Microsoft SQL server.

• This test queries the report server database to pull details related to the status of the report requests. For this, the test needs to connect to the report server database. To enable this connection, enter the IP address of the report server database against the Report Server Database IP parameter, enter the port at which the report server database listens against the Report Server Database Port parameter, and enter the name of the report server database against the Report Server Database Name parameter. To determine the database IP, port, and name, refer to Monitoring the Microsoft SQL Report Server document.

• To run queries on the report server database, the test requires to connect to the report server database as a user with SELECT permissions to the ExecutionLog, Catalog, runningjobs, and users tables of that database. For this purpose, you can create a special user on the Microsoft SQL server, grant the required monitoring privileges to that user, and configure the User and Password parameters with the credentials of that user. To know how to create such a user, refer to Monitoring the Microsoft SQL Report Server document.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• By default, none is displayed in the DOMAIN text box. If the ‘SQL server and Windows’ authentication has been enabled for the server being monitored, then the Domain can continue to be none. On the other hand, if ‘Windows only’ authentication has been enabled, then, in the Domain text box, specify the Windows domain in which the SSIS database that this test connects to exists. Also, in such a case, the User name and Password that you provide should be that of a user authorized to access the Microsoft SQL server hosting the SSIS database of interest.

• Specify the running duration (in seconds) of a report in the REPORT DURATION SECONDS text box, beyond which that report will be counted as a slow report.

• By default, the DD Row Count parameter is set to 10. This implies that by default the detailed diagnosis of the test reports the top-10 reports in terms of the running time of the reports. If you want detailed diagnosis to include more or less number of reports, then change the value of this parameter.

• To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.