All Unit Monitors in Microsoft.Amalga.UIS.2009.Monitoring Management Pack

 DisplayNameDescriptionIDTargetParent MonitorCategoryEnabledInstance NameCounter NameFrequencyAlert GenerateAlert SeverityAlert PriorityAlert Auto ResolveMonitor TypeRemotableAccessibilityRunAs
Microsoft.Amalga.UIS.2009.Monitoring.DADEDeleterMemoryUsage.MonitorDADE Deleter memory usageGenerates an alert when 1 or more DADE Deleter services consumes more memory than the configured threshold.Microsoft.Amalga.UIS.2009.Monitoring.DADEDeleterMemoryUsage.MonitorMicrosoft.Amalga.UIS.2009.DADEServerSystem.Health.PerformanceStatePerformanceHealthFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.Library.ProcessMemoryUsageMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.DADEFilerMemoryUsage.MonitorDADE Filer memory usageGenerates an alert when 1 or more DADE Filer services consumes more memory than the configured threshold.Microsoft.Amalga.UIS.2009.Monitoring.DADEFilerMemoryUsage.MonitorMicrosoft.Amalga.UIS.2009.DADEServerSystem.Health.PerformanceStatePerformanceHealthFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.Library.ProcessMemoryUsageMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.DADEFilerReceivingMessages.MonitorDADE Filer is receiving messagesThis monitor alerts when at least 1 message has not been received/processed within X minutes (X may be fixed or schedule dependent).Microsoft.Amalga.UIS.2009.Monitoring.DADEFilerReceivingMessages.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_FilerSystem.Health.AvailabilityStateAvailabilityHealthFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.UIS.2009.Monitoring.ReceivingMessages.MonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.DADEReceiverMemoryUsage.MonitorDADE Receiver memory usageGenerates an alert when 1 or more DADE Receiver services consumes more memory than the configured threshold.Microsoft.Amalga.UIS.2009.Monitoring.DADEReceiverMemoryUsage.MonitorMicrosoft.Amalga.UIS.2009.DADEServerSystem.Health.PerformanceStatePerformanceHealthFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.Library.ProcessMemoryUsageMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.DADEReceiverReceivingMessages.MonitorDADE Receiver is receiving messagesThis monitor alerts when at least 1 message has not been received/processed within X minutes (X may be fixed or schedule dependent).Microsoft.Amalga.UIS.2009.Monitoring.DADEReceiverReceivingMessages.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_ReceiverSystem.Health.AvailabilityStateAvailabilityHealthFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.UIS.2009.Monitoring.ReceivingMessages.MonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.Filer.43.52.Event.MonitorDADE Filer - Unable to connect to the databaseGenerates an alert when Filer event 43 (unable to connect to database) is generated. Alert closes when service reconnects (event 52) or when service is stopped or restarted. (events 0-6) Microsoft.Amalga.UIS.2009.Monitoring.Filer.43.52.Event.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_FilerSystem.Health.AvailabilityStateAlertFalse0TrueErrorNormalTrueMicrosoft.Windows.2SingleEventLog2StateMonitorTypeTruePublic
Microsoft.Amalga.UIS.2009.Monitoring.Filer.79.52.Event.MonitorDADE Filer - Error attempting to open SQL databaseGenerates an alert when Filer event 79 (cannot open SQL db) is generated. Alert closes when service reconnects (event 52) or when service is stopped or restarted. (events 0-6) Microsoft.Amalga.UIS.2009.Monitoring.Filer.79.52.Event.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_FilerSystem.Health.AvailabilityStateAlertTrue0TrueErrorNormalTrueMicrosoft.Windows.2SingleEventLog2StateMonitorTypeTruePublic
Microsoft.Amalga.UIS.2009.Monitoring.FilerErrorFolderCount.MonitorDADE Filer error folder is emptyGenerates an alert when a DADE Filer service has 1 or more messages in its Error folder.Microsoft.Amalga.UIS.2009.Monitoring.FilerErrorFolderCount.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_FilerSystem.Health.AvailabilityStateCustomTrue0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.Library.FileCountMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.FilerInboundFolderCount.MonitorDADE Filer - pending file count backlog is within toleranceMonitor DADE Filer count of pending files appears to be backloggingMicrosoft.Amalga.UIS.2009.Monitoring.FilerInboundFolderCount.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_FilerSystem.Health.PerformanceStatePerformanceHealthFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.Library.FileCountMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.PackageReceivingMessages.MonitorScript Engine Package is receiving messagesThis monitor alerts when at least 1 message has not been received/processed within X minutes (X may be fixed or schedule dependent).Microsoft.Amalga.UIS.2009.Monitoring.PackageReceivingMessages.MonitorMicrosoft.Amalga.UIS.2009.ScriptEnginePackageSystem.Health.AvailabilityStateAvailabilityHealthFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.UIS.2009.Monitoring.ReceivingMessages.MonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.PackageRunTime.MonitorScript Engine Package - Run Time CheckerAccording to the package's state file, the package is currently backlogged.Microsoft.Amalga.UIS.2009.Monitoring.PackageRunTime.MonitorMicrosoft.Amalga.UIS.2009.ScriptEnginePackageSystem.Health.PerformanceStatePerformanceHealthFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.UIS.2009.Monitoring.ScriptEnginePackageRunTimeChecker.MonitorTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.Receiver.49.50.Event.MonitorDADE Receiver - The connection terminated with the IP addressGenerates an alert when Receiver event 49 (connection terminated). Alert closes when service reconnects (event 50) or when service is stopped or restarted. (events 0, 37, 40-44)Microsoft.Amalga.UIS.2009.Monitoring.Receiver.49.50.Event.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_ReceiverSystem.Health.AvailabilityStateAvailabilityHealthFalse0TrueErrorNormalTrueMicrosoft.Windows.2SingleEventLog2StateMonitorTypeTruePublic
Microsoft.Amalga.UIS.2009.Monitoring.ReceiverErrorFolderCount.MonitorDADE Receiver error folder is emptyGenerates an alert when a DADE Receiver service has 1 or more messages in its Error folder.Microsoft.Amalga.UIS.2009.Monitoring.ReceiverErrorFolderCount.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_ReceiverSystem.Health.AvailabilityStateCustomTrue0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.Library.FileCountMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.ReceiverUTF8FileCount.MonitorDADE Receiver's Received\UTF8 folder is emptyThis monitor is meant to alert customers of a known issue with the DADE. See product knowledge for details on this monitor.Microsoft.Amalga.UIS.2009.Monitoring.ReceiverUTF8FileCount.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_ReceiverSystem.Health.PerformanceStatePerformanceHealthTrue0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.Library.FileCountMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.RetrieverOutboxFolderCount.MonitorDADE Retriever - pending file count backlog for outbox folder is within toleranceDADE Retriever - count of pending files for outbox folder appears to be backloggingMicrosoft.Amalga.UIS.2009.Monitoring.RetrieverOutboxFolderCount.MonitorMicrosoft.Amalga.UIS.2009.DADEServiceNode_RetrieverSystem.Health.PerformanceStatePerformanceHealthFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.Library.FileCountMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.ScriptEngine.PackageStopped.MonitorScript Engine Package is runningThe script engine package indicated is stopped. The package will no longer process data until restarted.Microsoft.Amalga.UIS.2009.Monitoring.ScriptEngine.PackageStopped.MonitorMicrosoft.Amalga.UIS.2009.ScriptEnginePackageSystem.Health.AvailabilityStateAvailabilityHealthTrueAmalga Script EnginePackage Stopped373TrueMatchMonitorHealthNormalTrueSystem.Performance.ThresholdMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.ScriptEngineMemoryUsage.MonitorScript Engine memory usageGenerates an alert when 1 or more Script Engine services consumes more memory than the configured threshold.Microsoft.Amalga.UIS.2009.Monitoring.ScriptEngineMemoryUsage.MonitorMicrosoft.Amalga.UIS.2009.ScriptEngineServerSystem.Health.PerformanceStateCustomFalse0TrueMatchMonitorHealthNormalTrueMicrosoft.Amalga.Library.ProcessMemoryUsageMonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.ServiceUpMonitorWindows service is running (node level, cluster aware)This monitor is MSCS cluster aware. For non-clustered services and clustered services that are active, the monitor will be green or red if the service is running or stopped. A passive service will show yellow regardless of running state. A disabled service will also show yellow. Yellow is not a warning state in this context. It is valid for a clustered service to be passive and stopped. A disabled service is also shown as yellow by this monitor. Yellow typically indicates a warning state in SCOM. To avoid rolling up Yellow to parent objects in the diagram view, a helper monitor was created to specifically promote this monitor's Yellow to a Green state during aggregate health rollup. See the knowledge under 'Helper Monitor - Promote Passive Node state from Yellow to Green' monitor for more details.Microsoft.Amalga.UIS.2009.Monitoring.ServiceUpMonitorMicrosoft.Amalga.UIS.2009.WindowsServiceNodeMicrosoft.Amalga.UIS.2009.Monitoring.ActiveNodeAggregateCustomTrue0TrueErrorNormalTrueMicrosoft.Amalga.Library.ServiceRunning.MonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount
Microsoft.Amalga.UIS.2009.Monitoring.ServiceUpMonitorActiveHelperHelper Monitor - Promote Passive or Disabled service's state from Yellow to GreenThis monitor is solely for the purpose of promoting a service's up/down state from Yellow to Green. Yellow can happen when the service is Passive or when the service startup mode is marked as Disabled. To avoid rolling up Yellow in the diagram view, this helper was constructed. A limitation in SCOM prevents the cluster-aware monitor from having 2 Green states in a 3-state monitor. To work around this, we must do a Best Of aggregate monitor using the cluster-aware up/down monitor + this helper monitor.Microsoft.Amalga.UIS.2009.Monitoring.ServiceUpMonitorActiveHelperMicrosoft.Amalga.UIS.2009.WindowsServiceNodeMicrosoft.Amalga.UIS.2009.Monitoring.ActiveNodeAggregateCustomTrue0FalseTrueMicrosoft.Amalga.Library.ServiceRunning.MonitorTypeTruePublicMicrosoft.Amalga.Library.Monitoring.RunAsAccount