All Rules in Microsoft.SQLServer.2016.IntegrationServices.Monitoring Management Pack

	DisplayName	Description	ID	Target	Category	Enabled	Instance Name	Counter Name	Frequency	Event_ID	Event Source	Alert Generate	Alert Severity	Alert Priority	Remotable	Event Log
	MSSQL 2016: SSIS 2016 Pipeline: Buffers Spooled	The number of buffers currently written to the disk. If the data flow engine runs low on physical memory, buffers not currently used are written to disk and then reloaded when needed. This counter is polled every fifteen minutes.	Microsoft.SQLServer.2016.IntegrationServices.PerformanceRule.Instance.PipelineBuffersSpooled	Microsoft.SQLServer.2016.IntegrationServices.Instance	PerformanceCollection	True	SQLServer:SSIS Pipeline 13.0	Buffers spooled	900	0		False			True
	MSSQL 2016: SSIS 2016 Pipeline: Rows Read	This counter indicates the number of rows that a source produces. The number does not include rows read from reference tables by the Lookup transformation. This counter is polled every fifteen minutes.	Microsoft.SQLServer.2016.IntegrationServices.PerformanceRule.Instance.PipelineRowsRead	Microsoft.SQLServer.2016.IntegrationServices.Instance	PerformanceCollection	True	SQLServer:SSIS Pipeline 13.0	Rows read	900	0		False			True
	MSSQL 2016: SSIS 2016 Pipeline: Rows Written	This counter displays the number of rows offered to a destination. The number does not reflect rows written to the destination data store. This counter is polled every fifteen minutes.	Microsoft.SQLServer.2016.IntegrationServices.PerformanceRule.Instance.PipelineRowsWritten	Microsoft.SQLServer.2016.IntegrationServices.Instance	PerformanceCollection	True	SQLServer:SSIS Pipeline 13.0	Rows written	900	0		False			True
	MSSQL 2016: IS Package Failed	A package failed during execution.	Microsoft.SQLServer.2016.IS_Package_Failed_5_Rule	Microsoft.SQLServer.2016.IntegrationServices.Instance	EventCollection	True			0	12291	SQLISPackage130	True	Error	Normal	True	Application
	MSSQL 2016: IS Service failed to load user defined Configuration file	The configuration file for the Integration Services service could not be loaded, when the services was started. By default, this file is named MSDtsSrvr.ini.xml. However, Integration Services can be configured by a registry setting to use any file name and file location.	Microsoft.SQLServer.2016.IS_Service_failed_to_load_user_defined_Configuration_file_5_Rule	Microsoft.SQLServer.2016.IntegrationServices.Instance	EventCollection	True			0	272	SQLISService130	True	Error	Normal	True	Application
	MSSQL 2016: IS Service has attempted to stop a running package	The Integration Services service was used to send a request to the Integration Services runtime to stop a running package. Note: This rule is disabled by default. Please use overrides to enable it when necessary.	Microsoft.SQLServer.2016.IS_Service_has_attempted_to_stop_a_running_package_5_Rule	Microsoft.SQLServer.2016.IntegrationServices.Instance	EventCollection	False			0	336	SQLISService130	True	Error	Normal	True	Application
	MSSQL 2016: Package execution failed because the checkpoint file cannot be loaded	A package that is configured to use checkpoints and to always use the checkpoint file failed to restart.	Microsoft.SQLServer.2016.Package_execution_failed_because_the_checkpoint_file_cannot_be_loaded_5_Rule	Microsoft.SQLServer.2016.IntegrationServices.Instance	EventCollection	True			0	12550	SQLISPackage130	True	Error	Normal	True	Application
	MSSQL 2016: The package restarted from checkpoint file. Package was configured to restart from checkpoint and it did	A package configured to use checkpoints failed and then restarted from the point of failure using the checkpoint file.	Microsoft.SQLServer.2016.The_package_restarted_from_checkpoint_file.__Package_was_configured_to_restart_from_checkpoint_and_it_did_5_Rule	Microsoft.SQLServer.2016.IntegrationServices.Instance	EventCollection	True			0	12558	SQLISPackage130	True	Error	Normal	True	Application