Unit Monitors

Name Enabled Target Class Alert Message Description
Unit Monitor   DADE Deleter memory usage
0
 
Amalga 2009 DADE Server Role DADE Deleter memory usage is above threshold Generates an alert when 1 or more DADE Deleter services consumes more memory than the configured threshold.
Unit Monitor   DADE Filer - Error attempting to open SQL database onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Error attempting to open SQL database Generates 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)
Unit Monitor   DADE Filer - pending file count backlog is within tolerance
0
 
Amalga 2009 DADE Service - Filer (node) DADE Filer - count of pending files appears to be backlogging Monitor DADE Filer count of pending files appears to be backlogging
Unit Monitor   DADE Filer - Unable to connect to the database
0
 
Amalga 2009 DADE Service - Filer (node) DADE Filer - Unable to connect to the database Generates 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)
Unit Monitor   DADE Filer error folder is empty onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer error folder is not empty Generates an alert when a DADE Filer service has 1 or more messages in its Error folder.
Unit Monitor   DADE Filer is receiving messages
0
 
Amalga 2009 DADE Service - Filer (node) DADE Filer is not receiving messages This monitor alerts when at least 1 message has not been received/processed within X minutes (X may be fixed or schedule dependent).
Unit Monitor   DADE Filer memory usage
0
 
Amalga 2009 DADE Server Role DADE Filer memory usage is above threshold Generates an alert when 1 or more DADE Filer services consumes more memory than the configured threshold.
Unit Monitor   DADE Receiver - The connection terminated with the IP address
0
 
Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The connection terminated with the IP address Generates 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)
Unit Monitor   DADE Receiver error folder is empty onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver error folder is not empty Generates an alert when a DADE Receiver service has 1 or more messages in its Error folder.
Unit Monitor   DADE Receiver is receiving messages
0
 
Amalga 2009 DADE Service - Receiver (node) DADE Receiver is not receiving messages This monitor alerts when at least 1 message has not been received/processed within X minutes (X may be fixed or schedule dependent).
Unit Monitor   DADE Receiver memory usage
0
 
Amalga 2009 DADE Server Role DADE Receiver memory usage is above threshold Generates an alert when 1 or more DADE Receiver services consumes more memory than the configured threshold.
Unit Monitor   DADE Receiver's Received\UTF8 folder is empty onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver's Received\UTF8 folder is not empty This monitor is meant to alert customers of a known issue with the DADE. See product knowledge for details on this monitor.
Unit Monitor   DADE Retriever - pending file count backlog for outbox folder is within tolerance
0
 
Amalga 2009 DADE Service - Retriever (node) DADE Retriever - count of pending files for outbox folder appears to be backlogging DADE Retriever - count of pending files for outbox folder appears to be backlogging
Unit Monitor   Helper Monitor - Promote Passive or Disabled service's state from Yellow to Green onEssentialMonitoring Amalga 2009 Windows Service Node   This 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.
Unit Monitor   Script Engine memory usage
0
 
Amalga 2009 Script Engine Server Role Script Engine memory usage is above threshold Generates an alert when 1 or more Script Engine services consumes more memory than the configured threshold.
Unit Monitor   Script Engine Package - Run Time Checker
0
 
Amalga 2009 Script Engine Package Script Engine Package is running behind (processing a backlog) According to the package's state file, the package is currently backlogged.
Unit Monitor   Script Engine Package is receiving messages
0
 
Amalga 2009 Script Engine Package Script Engine Package is not receiving messages This monitor alerts when at least 1 message has not been received/processed within X minutes (X may be fixed or schedule dependent).
Unit Monitor   Script Engine Package is running onEssentialMonitoring Amalga 2009 Script Engine Package Script Engine Package is stopped The script engine package indicated is stopped. The package will no longer process data until restarted.
Unit Monitor   Windows service is running (node level, cluster aware) onEssentialMonitoring Amalga 2009 Windows Service Node Windows service is stopped 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.

See Also for Amalga UIS 2009 Monitoring Management Pack


Downloads for Amalga UIS 2009 Monitoring Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED