All Unit Monitors in Microsoft.SQLServer.2016.ReportingServices.Monitoring Management Pack

 DisplayNameDescriptionIDTargetParent MonitorCategoryEnabledInstance NameCounter NameFrequencyAlert GenerateAlert SeverityAlert PriorityAlert Auto ResolveMonitor TypeRemotableAccessibilityRunAs
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Deployment.AllInstancesAreDiscoveredAll deployment instances are discoveredThe monitor raises an alert, if not all SSRS Instances are discovered for the given SSRS Deployment.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Deployment.AllInstancesAreDiscoveredMicrosoft.SQLServer.2016.ReportingServices.DeploymentSystem.Health.ConfigurationStateConfigurationHealthTrue0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Deployment.AllInstancesAreDiscoveredTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.DeploymentWatcher.DBConnectionDatabase accessibleThe monitor changes its state and raises an alert, if the deployment watcher fails to connect to Reporting Services DatabaseMicrosoft.SQLServer.2016.ReportingServices.UnitMonitor.DeploymentWatcher.DBConnectionMicrosoft.SQLServer.2016.ReportingServices.DeploymentWatcherSystem.Health.AvailabilityStatePerformanceHealthTrue0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.DBConnectionMonitorTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.DeploymentWatcher.MisconfiguredDataSourcesMisconfigured data sourcesThe monitor alerts, if misconfigured data sources are detected.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.DeploymentWatcher.MisconfiguredDataSourcesMicrosoft.SQLServer.2016.ReportingServices.DeploymentWatcherSystem.Health.ConfigurationStateConfigurationHealthTrue0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.DeploymentWatcher.MisconfiguredDataSourcesTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.DeploymentWatcher.NumberOfFailedReportExecutionsNumber of failed report executionsThe monitor alerts, if the number of failed report executions expressed as a percentage of total number of report executions is higher than the threshold. The monitor will raise an alert and change its state only when several consecutive checks have failed.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.DeploymentWatcher.NumberOfFailedReportExecutionsMicrosoft.SQLServer.2016.ReportingServices.DeploymentWatcherSystem.Health.PerformanceStatePerformanceHealthTrue0TrueWarningNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.DeploymentWatcher.NumberOfFailedReportExecutionsTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.DeploymentWatcher.TempDBConnectionTemporary database accessibleThe monitor raises an alert, if the deployment watcher fails to connect to Reporting Services Temporary Database.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.DeploymentWatcher.TempDBConnectionMicrosoft.SQLServer.2016.ReportingServices.DeploymentWatcherSystem.Health.AvailabilityStatePerformanceHealthTrue0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.DBConnectionMonitorTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.ConfigurationConflictWithSQLServerConfiguration conflict with SQL ServerThe monitor alerts, if there is a SQL Server process running on the server, and WorkingSetMaximum setting for the SSRS Instance does not allow enough memory for the SQL server process. Note: This monitor is disabled by default. Please use overrides to enable it when necessary.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.ConfigurationConflictWithSQLServerMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.ConfigurationStateConfigurationHealthFalse0TrueWarningNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.ConfigurationConflictWithSQLServerTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.CpuUsageByInstanceCPU utilization (\%)The monitor alerts, if the CPU usage by the SSRS process is close to 100\%.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.CpuUsageByInstanceMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.PerformanceStatePerformanceHealthTrue0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.CpuUsageByInstanceTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.DBConnectionDatabase accessibleThe monitor raises an alert, if the monitoring workflow cannot access the Reporting Services Database. Note: This monitor is disabled by default. Please use overrides to enable it when necessary.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.DBConnectionMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.AvailabilityStatePerformanceHealthFalse0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.DBConnectionMonitorTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.InstanceConfigurationInstance configuration stateThe monitor raises an alert, if SSRS instance has certain configuration problems.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.InstanceConfigurationMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.ConfigurationStateConfigurationHealthFalse0TrueWarningNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.InstanceConfigurationTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.MemoryUsageByInstanceMemory consumed by SSRS InstanceThe monitor alerts, if the memory usage by the SSRS process is close to the limit defined by WorkingSetMaximum setting.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.MemoryUsageByInstanceMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.PerformanceStatePerformanceHealthTrue0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.MemoryUsageByInstanceTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.MemoryUsageOnServerMemory consumed by othersThe monitor alerts, if the memory consumed by processes other than SSRS does not allow SSRS to allocate the amount of memory prescribed by WorkingSetMinimum setting. The monitor uses the following formula to determine the state: ({WorkingSetMinimum} + {Memory Consumed By Others})*100/{Total Memory} < {Threshold (\%)}Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.MemoryUsageOnServerMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.PerformanceStatePerformanceHealthTrue0TrueWarningNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.MemoryUsageOnServerTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.ReportsExecutionFailureNumber of failed report executionsThe monitor checks, if the number of failed report executions per minute does not exceed the threshold expressed as an absolute value. The monitor will raise an alert and change its state only when several consecutive checks have failed. Note: This monitor is disabled by default. Please use overrides to enable it when necessary.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.ReportsExecutionFailureMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.PerformanceStatePerformanceHealthFalse0TrueWarningNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.ReportsExecutionFailureTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.SsrsReportManagerAccessibleReport manager accessibleThe monitor raises an alert, if monitoring workflow cannot connect to SSRS Report ManagerMicrosoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.SsrsReportManagerAccessibleMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.AvailabilityStatePerformanceHealthTrue0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.WebServiceAccessibleMonitorTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.SsrsWebServiceAccessibleWeb service accessibleThe monitor raises an alert, if monitoring workflow cannot connect to SSRS web service.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.SsrsWebServiceAccessibleMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.AvailabilityStatePerformanceHealthTrue0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.WebServiceAccessibleMonitorTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.TempDBConnectionTemporary database accessibleThe monitor raises an alert, if the instance failed to connect to Reporting Services Temporary Database. Note: This monitor is disabled by default. Please use overrides to enable it when necessary.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.Instance.TempDBConnectionMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.AvailabilityStatePerformanceHealthFalse0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.DBConnectionMonitorTruePublic
Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.WindowsServiceStateWindows service stateThe monitor alerts, if SSRS Windows service is not in running state for a longer period than the threshold.Microsoft.SQLServer.2016.ReportingServices.UnitMonitor.WindowsServiceStateMicrosoft.SQLServer.2016.ReportingServices.InstanceSystem.Health.AvailabilityStateAvailabilityHealthTrue0TrueErrorNormalTrueMicrosoft.SQLServer.2016.ReportingServices.MonitorType.Instance.WindowsServiceStateTruePublic