Rules

Name Enabled Target Class Description
  Alert: Amalga - Filer\Bytes Per Second (Shift 1)
0
 
Amalga 2009 DADE Service - Filer Records the service activity rate as the number of bytes processed per second. Shift 1 is configured to run Monday through Friday between the hours of 9 AM and 5 PM. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Filer\Bytes Per Second (Shift 2)
0
 
Amalga 2009 DADE Service - Filer Records the service activity rate as the number of bytes processed per second. Shift 2 is configured to run Monday through Saturday between the hours of 5 PM and 1 AM of the following day. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Filer\Bytes Per Second (Shift 3)
0
 
Amalga 2009 DADE Service - Filer Records the service activity rate as the number of bytes processed per second. Shift 3 is configured to run Monday through Friday between the hours of 1 AM and 9 AM. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Filer\Message Enqueue Time
0
 
Amalga 2009 DADE Service - Filer Records the amount of time the service took to insert the last message into the message queue.
  Alert: Amalga - Filer\Message Process Time
0
 
Amalga 2009 DADE Service - Filer Records the time spent to process the last message.
  Alert: Amalga - Filer\Messages Per Second (Shift 1)
0
 
Amalga 2009 DADE Service - Filer Records the service activity rate as the number of messages filed processed per second. Shift 1 is configured to run Monday through Friday between the hours of 9 AM and 5 PM. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Filer\Messages Per Second (Shift 2)
0
 
Amalga 2009 DADE Service - Filer Records the service activity rate as the number of messages filed processed per second. Shift 2 is configured to run Monday through Saturday between the hours of 5 PM and 1 AM of the following day. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Filer\Messages Per Second (Shift 3)
0
 
Amalga 2009 DADE Service - Filer Records the service activity rate as the number of messages filed processed per second. Shift 3 is configured to run Monday through Friday between the hours of 1 AM and 9 AM. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Receiver\Bytes Per Second (Shift 1)
0
 
Amalga 2009 DADE Service - Receiver Records the service activity rate as the number bytes received per second. Shift 1 is configured to run Monday through Friday between the hours of 9 AM and 5 PM. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Receiver\Bytes Per Second (Shift 2)
0
 
Amalga 2009 DADE Service - Receiver Records the service activity rate as the number bytes received per second. Shift 2 is configured to run Monday through Saturday between the hours of 5 PM and 1 AM of the following day. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Receiver\Bytes Per Second (Shift 3)
0
 
Amalga 2009 DADE Service - Receiver Records the service activity rate as the number bytes received per second. Shift 3 is configured to run Monday through Friday between the hours of 1 AM and 9 AM. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Receiver\Message Process Time
0
 
Amalga 2009 DADE Service - Receiver Records the amount of time the service took to process the last message.
  Alert: Amalga - Receiver\Messages Per Second (Shift 1)
0
 
Amalga 2009 DADE Service - Receiver Records the service activity rate as the number of messages received per second. Shift 1 is configured to run Monday through Friday between the hours of 9 AM and 5 PM. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Receiver\Messages Per Second (Shift 2)
0
 
Amalga 2009 DADE Service - Receiver Records the service activity rate as the number of messages received per second. Shift 2 is configured to run Monday through Saturday between the hours of 5 PM and 1 AM of the following day. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: Amalga - Receiver\Messages Per Second (Shift 3)
0
 
Amalga 2009 DADE Service - Receiver Records the service activity rate as the number of messages received per second. Shift 3 is configured to run Monday through Friday between the hours of 1 AM and 9 AM. When configuring the Days Of Week Mask in the monitor, you can determine the appropriate value by using the following values for each day of the week: Su-1, M-2, T-4, W-8, Th-16, F-32, Sa-64. Just add the values for the days you want the monitor to run. If you want all days of the week, they will add up to 127. If you just want Sunday, the value is 1. Just Tuesday and Thursday would be 20. M-F is 62.
  Alert: DADE Filer - An exception occurred attempting to move a file to the Error folder onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - An exception occurred attempting to move a file to the Error folder. [DADE Filer: Event ID 62]
  Alert: DADE Filer - Duplicate registry value specified for Folder Path onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Duplicate registry value specified for Folder Path. [DADE Filer: Event ID 30]
  Alert: DADE Filer - Error finding file indicated in the registry entry for Script Path onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Error finding file indicated in the registry entry for Script Path [DADE Filer: Event ID 36]
  Alert: DADE Filer - Exception Error while executing Feed Script onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Exception Error while executing Feed Script. [DADE Filer: Event ID 66]
  Alert: DADE Filer - Exception occurred while attempting to read files from directory onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Exception occurred while attempting to read files from directory. [DADE Filer Event ID 44]
  Alert: DADE Filer - Exception occurred while moving a file to the Filed folder onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Exception occurred while moving a file to the Filed folder [DADE Filer: Event ID 56]
  Alert: DADE Filer - Feed Script Engine encountered an Exception Error while processing Script Key onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Feed Script Engine encountered an Exception Error while processing Script Key. [DADE Filer: Event ID 69]
  Alert: DADE Filer - Internal exception encountered in the message script onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Internal exception encountered in the message script [DADE Filer: Event ID 35]
  Alert: DADE Filer - Problem accessing the file specified in the registry onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Problem accessing the file specified in the registry [DADE Filer Event ID 21]
  Alert: DADE Filer - Script indicated not to send file to database (file moving to Error Folder)
0
 
Amalga 2009 DADE Service - Filer (node) DADE Filer - Script indicated not to send file to database (file moving to Error Folder). [DADE Filer: Event ID 60]
  Alert: DADE Filer - The drive specified in the registry is not valid onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The drive specified in the registry is not valid. [DADE Filer: Event ID 8]
  Alert: DADE Filer - The feed script returned an error onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The feed script returned an error. [DADE Filer: Event ID 68]
  Alert: DADE Filer - The format before the message script signature is invalid onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The format before the message script signature is invalid [DADE Filer: Event ID 34]
  Alert: DADE Filer - The log level specified in registry is not valid onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The log level specified in registry is not valid [DADE Filer: Event ID 10]
  Alert: DADE Filer - The registry entry for Filer Log is not '0' or '1' onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The registry entry for Filer Log is not '0' or '1' [DADE Filer: Event ID 23]
  Alert: DADE Filer - The registry entry for Folder Scan Time Seconds is less than 1 onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The registry entry for Folder Scan Time Seconds is less than 1 [DADE Filer: Event ID 28]
  Alert: DADE Filer - The registry entry for Folder Scan Time Seconds is not an integer onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The registry entry for Folder Scan Time Seconds is not an integer [DADE Filer: Event ID 29]
  Alert: DADE Filer - The registry entry for Script Language is not 'CSHARP' or 'VB.NET' onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The registry entry for Script Language is not 'CSHARP' or 'VB.NET' [DADE Filer: Event ID 24]
  Alert: DADE Filer - The registry value for Log File Path has no data onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The registry value for Log File Path has no data [DADE Filer: Event ID 22]
  Alert: DADE Filer - The script returned NULL onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - The script returned NULL. [DADE Filer: Event ID 67]
  Alert: DADE Filer - Unable to open the feed-specific log file onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Unable to open the feed-specific log file. [DADE Filer: Event ID 71]
  Alert: DADE Filer - Unable to process file
0
 
Amalga 2009 DADE Service - Filer (node) DADE Filer - Unable to process file. [DADE Filer: Event ID 57]
  Alert: DADE Filer - Unable to read the registry onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) DADE Filer - Unable to read the registry. [DADE Filer: Event ID 31]
  Alert: DADE Receiver - Error encountered while saving Message onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Error encountered while saving Message [DADE Receiver: Event ID 71]
  Alert: DADE Receiver - Error finding the file indicated in the registry for Script Path onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Error finding the file indicated in the registry for Script Path [DADE Receiver: Event ID 34]
  Alert: DADE Receiver - Error while attempting to open socket onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Error while attempting to open socket [DADE Receiver: Event ID 67]
  Alert: DADE Receiver - Exception encountered with value in the registry for Script Path onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Exception encountered with value in the registry for Script Path [DADE Receiver: Event ID 35]
  Alert: DADE Receiver - Exception Error while executing Feed Script onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Exception Error while executing Feed Script [DADE Receiver: Event ID 62]
  Alert: DADE Receiver - Feed Script Engine encountered an Exception Error while processing Script Key onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Feed Script Engine encountered an Exception Error while processing Script Key [DADE Receiver: Event ID 58]
  Alert: DADE Receiver - Feed Script reported an error while processing Received Message onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Feed Script reported an error while processing Received Message [DADE Receiver: Event ID 61]
  Alert: DADE Receiver - Internal exception encountered in the message script onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Internal exception encountered in the message script [DADE Receiver: Event ID 32]
  Alert: DADE Receiver - Internal exception encountered in the message script onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Internal exception encountered in the message script [DADE Receiver: Event ID 33]
  Alert: DADE Receiver - Problem accessing the file specified as Log File Path onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Problem accessing the file specified as Log File Path. [DADE Receiver: Event ID 16]
  Alert: DADE Receiver - The feed script returned an error onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The feed script returned an error [DADE Receiver: Event ID 57]
  Alert: DADE Receiver - The log level specified in the registry for Log Level is not valid onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The log level specified in the registry for Log Level is not valid. DADE Receiver: Event ID 15]
  Alert: DADE Receiver - The registry entries for Marker Stop and Marker Start are the same onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entries for Marker Stop and Marker Start are the same. [DADE Receiver: Event ID 12]
  Alert: DADE Receiver - The registry entry for Client Connected Timeout is not an integer onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Client Connected Timeout is not an integer [DADE Receiver: Event ID 5]
  Alert: DADE Receiver - The registry entry for Client Connected Timeout is not greater or equal to 0 onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Client Connected Timeout is not greater or equal to 0 [DADE Receiver: Event ID 4]
  Alert: DADE Receiver - The registry entry for Log Duplicates is not valid onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Log Duplicates is not valid. [DADE Receiver: Event ID 18]
  Alert: DADE Receiver - The registry entry for Log File Path has no data onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Log File Path has no data. [DADE Receiver: Event ID 17]
  Alert: DADE Receiver - The registry entry for Marker Keep is not valid onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Marker Keep is not valid. [DADE Receiver: Event ID 13]
  Alert: DADE Receiver - The registry entry for Port is not an integer onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Port is not an integer [DADE Receiver: Event ID 6]
  Alert: DADE Receiver - The registry entry for Script Language is not 'CSHARP' or 'VB.NET' onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Script Language is not 'CSHARP' or 'VB.NET'. [DADE Receiver: Event ID 14]
  Alert: DADE Receiver - The registry entry for Sequence High is not an integer onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Sequence High is not an integer. [DADE Receiver" Event ID 1]
  Alert: DADE Receiver - The registry entry for Sequence High is not greater than Sequence Low onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Sequence High is not greater than Sequence Low [DADE Receiver: Event ID 3]
  Alert: DADE Receiver - The registry entry for Sequence Low is not an integer onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry entry for Sequence Low is not an integer [DADE Receiver: Event ID 2]
  Alert: DADE Receiver - The registry value for Marker Start has no data onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry value for Marker Start has no data. [DADE Receiver: Event ID 11]
  Alert: DADE Receiver - The registry value for Marker Stop has no data onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The registry value for Marker Stop has no data. [DADE Receiver: Event ID 10]
  Alert: DADE Receiver - The service cannot open the feed-specific log file onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - The service cannot open the feed-specific log file [DADE Receiver: Event ID 63]
  Alert: DADE Receiver - Unable to read the registry onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) DADE Receiver - Unable to read the registry. [DADE Receiver: Event ID 19]
  Alert: Amalga ID - Auto-Resolved Parent-Child Inconsistency onEssentialMonitoring Amalga 2009 Script Engine Server Role Generates an alert when Event ID 2 (for Amalga ID) is encountered (Auto-Resolved Parent-Child Inconsistency)
  Alert: Amalga ID - Unresolved Parent-Child Inconsistency onEssentialMonitoring Amalga 2009 Script Engine Server Role Generates an alert when Amalga ID Event Id 1 is encountered (Unresolved Parent-Child Inconsistency)
  Event Collection: DADE Deleter Configuration Events onEssentialMonitoring Amalga 2009 DADE Service - Deleter (node) Collect DADE Deleter Configuration Events. [DADE Deleter: Event ID 1, 3-25, 27, 29 34, 37, 39]
  Event Collection: DADE Deleter Permissions Events onEssentialMonitoring Amalga 2009 DADE Service - Deleter (node) Collect DADE Deleter Permissions Events. [DADE Deleter: Event ID 2, 26, 28, 36, 38]
  Event Collection: DADE Deleter Service Status Events onEssentialMonitoring Amalga 2009 DADE Service - Deleter (node) Collect DADE Deleter Service Status Events
  Event Collection: DADE Deleter System Events onEssentialMonitoring Amalga 2009 DADE Service - Deleter (node) Collect DADE Deleter System Events. [DADE Deleter: Event ID 35]
  Event Collection: DADE Filer Configuration Events onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) Collect DADE Filer Configuration Events [DADE Filer: Event ID 10-15, 18, 20, 22-24, 28-30, 32, 38]
  Event Collection: DADE Filer DB Connectivity Events onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) Collect DADE Filer DB Connectivity Events [DADE Filer: 74-78, 81, 84-98]
  Event Collection: DADE Filer Permissions Events onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) Collect DADE Filer Permissions Events [DADE Filer: 8, 17, 19, 21, 31, 33]
  Event Collection: DADE Filer Script Issues Events onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) Collect DADE Filer Script Issues Events [DADE Filer: 34-37, 66-73]
  Event Collection: DADE Filer Service Events onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) Collect DADE Filer Service Events. DADE Filer: Event ID 41, 42, 44-51, 53-56, 58-64, 99]
  Event Collection: DADE Filer Service Status Events onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) Collect DADE Filer Service Status Events. [DADE Filer: Event ID 1-7, 39, 40]
  Event Collection: DADE Filer System Events onEssentialMonitoring Amalga 2009 DADE Service - Filer (node) Collect DADE Filer System Events. [DADE Filer: Event ID 16]
  Event Collection: DADE Receiver Configuration Events onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) Collect DADE Receiver Configuration Events. [DADE Receiver: Event ID 1-7, 10-18, 20, 22-26, 29, 31, 34]
  Event Collection: DADE Receiver Permissions Events onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) Collect DADE Receiver Permissions Events. [DADE Receiver: Event ID 8, 9, 19, 21, 28, 30]
  Event Collection: DADE Receiver Script Issues Events onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) Collect DADE Receiver Script Issues Events. [DADE Receiver: Event ID 32, 33, 35]
  Event Collection: DADE Receiver Service Events onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) Collect DADE Receiver Service Events. [DADE Receiver: Event ID 47, 48, 51-76]
  Event Collection: DADE Receiver Service Status Events onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) Collect DADE Receiver Service Status Events. [DADE Receiver: Event ID 36-46]
  Event Collection: DADE Receiver System Events onEssentialMonitoring Amalga 2009 DADE Service - Receiver (node) Collect DADE Receiver System Events. [DADE Receiver: Event ID 27]
  Event Collection: Amalga ID Events onEssentialMonitoring Amalga 2009 Script Engine Server Role This rule collects Amalga ID events - typically identifier consistency issues detected by Amalga ID. [Amalga ID: Event ID 1-3]
  Package Error: Ignoring error and continuing onEssentialMonitoring Amalga 2009 Script Engine Package Package Error: Ignoring error and continuing. [Parser: Event ID 9]
  Package Error: Ignoring error and continuing onEssentialMonitoring Amalga 2009 Script Engine Package Package Error: Ignoring error and continuing. [Parser: Event ID 9]
  Package Error: Ignoring error and continuing onEssentialMonitoring Amalga 2009 Script Engine Service Node Package error. Ignoring error and continuing. [Parser: Event ID 9]
  Package Error: Retrying current message onEssentialMonitoring Amalga 2009 Script Engine Package Package Error: Retrying current message. [Parser: Event ID 8]
  Package Error: Retrying current message onEssentialMonitoring Amalga 2009 Script Engine Package Package Error: Retrying current message. [Parser: Event ID 8]
  Package Error: Retrying current message onEssentialMonitoring Amalga 2009 Script Engine Service Node Package error. Retrying current message. [Parser: Event ID 8]
  Package Error: Skipping current message onEssentialMonitoring Amalga 2009 Script Engine Package Package Error: Skipping current message. [Parser: Event ID 7]
  Package Error: Skipping current message onEssentialMonitoring Amalga 2009 Script Engine Package Package error. Skipping current message. [Parser: Event ID 7]
  Package Error: Skipping current message onEssentialMonitoring Amalga 2009 Script Engine Service Node Package Error: Skipping current message. [Parser: Event ID 7]
  Package Error: Stop encountered. Messages no longer processed for this package until next restart.
0
 
Amalga 2009 Script Engine Package Package error. Stop encountered. Messages will no longer be processed for this package until next restart. [Parser: Event ID 6]
  Package Error: Stop encountered. Messages no longer processed for this package until next restart. onEssentialMonitoring Amalga 2009 Script Engine Service Node Package error. Stop encountered. Messages will no longer be processed for this package until next restart. [Parser: Event ID 6]
  Package Info: The service loaded a package successfully onEssentialMonitoring Amalga 2009 Script Engine Package The service loaded a package successfully. [Parser: Event ID 5]
  Package or Service Error: Ignoring error and continuing onEssentialMonitoring Amalga 2009 Script Engine Package Package or Service Error: Ignoring error and continuing. [Parser: Event ID 13]
  Package or Service Error: Ignoring error and continuing onEssentialMonitoring Amalga 2009 Script Engine Package Package or Service Error: Ignoring error and continuing. [Parser: Event ID 13]
  Package or Service Error: Ignoring error and continuing onEssentialMonitoring Amalga 2009 Script Engine Service Node Package or service error. An error occurred with the package or the service. Ignoring error and continuing. [Parser: Event ID 13]
  Package or Service Error: Retrying current message onEssentialMonitoring Amalga 2009 Script Engine Package Package or Service Error: Retrying current message. [Parser: Event ID 12]
  Package or Service Error: Retrying current message onEssentialMonitoring Amalga 2009 Script Engine Package Package or Service Error: Retrying current message. [Parser: Event ID 12]
  Package or Service Error: Retrying current message onEssentialMonitoring Amalga 2009 Script Engine Service Node Package or service error. An error occurred with the package or the service. Retrying current message. [Parser: Event ID 12]
  Package or Service Error: Skipping current message onEssentialMonitoring Amalga 2009 Script Engine Package Package or Service Error: Skipping current message. [Parser: Event ID 11]
  Package or Service Error: Skipping current message onEssentialMonitoring Amalga 2009 Script Engine Package Package or Service Error: Skipping current message. [Parser: Event ID 11]
  Package or Service Error: Skipping current message onEssentialMonitoring Amalga 2009 Script Engine Service Node Package or service error. An error occurred with the package or the service. Skipping current message. [Parser: Event ID 11]
  Package or Service Error: Stop encountered. Messages will no longer be processed until next restart onEssentialMonitoring Amalga 2009 Script Engine Service Node Package or service error. Stop encountered. An error occurred with the package or the service. Messages will no longer be processed until next restart. [Parser: Event ID 10]
  Package or Service Error: Stop encountered. Messages will no longer be processed until next restart. onEssentialMonitoring Amalga 2009 Script Engine Package Package or service error. Stop encountered. An error occurred with the package or the service. Messages will no longer be processed until next restart. [Parser: Event ID 10]
  Performance Collection: Amalga - Deleter\Files Deleted onEssentialMonitoring Amalga 2009 DADE Service - Deleter Records the total number of files deleted by the service since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Deleter\Root Subfolders Deleted onEssentialMonitoring Amalga 2009 DADE Service - Deleter Records the total number of subfolders deleted by the service since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Deleter\Service Heartbeat onEssentialMonitoring Amalga 2009 DADE Service - Deleter A counter incremented at 30-second intervals to demonstrate that the service is still active.
  Performance Collection: Amalga - Deleter\Start Attempts onEssentialMonitoring Amalga 2009 DADE Service - Deleter Records the number of attempts to start the service since the feed was installed.
  Performance Collection: Amalga - Deleter\Start Successes onEssentialMonitoring Amalga 2009 DADE Service - Deleter Records the number of times the service started successfully since the feed was installed.
  Performance Collection: Amalga - Filer\Bytes Per Second onEssentialMonitoring Amalga 2009 DADE Service - Filer Records the service activity rate as the number of bytes processed per second.
  Performance Collection: Amalga - Filer\Files Filed onEssentialMonitoring Amalga 2009 DADE Service - Filer Records the total number of files that the service filed since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Filer\Files Scanned onEssentialMonitoring Amalga 2009 DADE Service - Filer Records the total number of files scanned by the service since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Filer\Files Validated onEssentialMonitoring Amalga 2009 DADE Service - Filer Records the total number of files validated by the service since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Filer\Files With Errors onEssentialMonitoring Amalga 2009 DADE Service - Filer Records the total number of files that the service determined to be invalid since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Filer\Inbound Activity onEssentialMonitoring Amalga 2009 DADE Service - Filer This counter measures inbound network traffic. It is not a byte or message counter. The actual value has no statistical interest.
  Performance Collection: Amalga - Filer\Message Enqueue Time
0
 
Amalga 2009 DADE Service - Filer Records the amount of time the service took to insert the last message into the message queue.
  Performance Collection: Amalga - Filer\Message Process Time
0
 
Amalga 2009 DADE Service - Filer Records the time spent to process the last message.
  Performance Collection: Amalga - Filer\Messages Per Second onEssentialMonitoring Amalga 2009 DADE Service - Filer Records the service activity rate as the number of messages filed processed per second.
  Performance Collection: Amalga - Filer\Service Heartbeat onEssentialMonitoring Amalga 2009 DADE Service - Filer A counter incremented at 30-second intervals to demonstrate that the service is still active.
  Performance Collection: Amalga - Filer\Start Attempts onEssentialMonitoring Amalga 2009 DADE Service - Filer Records the number of attempts to start the service since the feed was installed.
  Performance Collection: Amalga - Filer\Start Successes onEssentialMonitoring Amalga 2009 DADE Service - Filer Records the number of times the service was started successfully since the feed was installed.
  Performance Collection: Amalga - Receiver\Bytes Per Second onEssentialMonitoring Amalga 2009 DADE Service - Receiver Records the service activity rate as the number bytes received per second.
  Performance Collection: Amalga - Receiver\Files Received onEssentialMonitoring Amalga 2009 DADE Service - Receiver Records the total number of files received by the service since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Receiver\Files Validated onEssentialMonitoring Amalga 2009 DADE Service - Receiver Records the total number of files validated by the service since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Receiver\Files With Errors onEssentialMonitoring Amalga 2009 DADE Service - Receiver Records the total number of files that the service determined to be invalid since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Receiver\Inbound Activity onEssentialMonitoring Amalga 2009 DADE Service - Receiver This counter measures inbound network traffic. It is not a byte or message counter. The actual value has no statistical interest.
  Performance Collection: Amalga - Receiver\Message Process Time
0
 
Amalga 2009 DADE Service - Receiver Records the amount of time the service took to process the last message.
  Performance Collection: Amalga - Receiver\Messages Discarded onEssentialMonitoring Amalga 2009 DADE Service - Receiver Records the total number of messages discarded by the service since the feed was installed. This counter is never reset.
  Performance Collection: Amalga - Receiver\Messages Per Second onEssentialMonitoring Amalga 2009 DADE Service - Receiver Records the service activity rate as the number of messages received per second.
  Performance Collection: Amalga - Receiver\Service Heartbeat onEssentialMonitoring Amalga 2009 DADE Service - Receiver A counter incremented at 30-second intervals to demonstrate that the service is still active.
  Performance Collection: Amalga - Receiver\Start Attempts onEssentialMonitoring Amalga 2009 DADE Service - Receiver The number of attempts to start the service since the feed was installed.
  Performance Collection: Amalga - Receiver\Start Successes onEssentialMonitoring Amalga 2009 DADE Service - Receiver The number of times the service started successfully since the feed was installed.
  Performance Collection: Amalga Query Processor\Query Processor Requests Per Second onEssentialMonitoring Amalga 2009 Middle Tier Role Collect Amalga Query Processor\Query Processor Requests Per Second
  Performance Collection: Amalga Query Processor\Query Processor Stored Queries Per Second onEssentialMonitoring Amalga 2009 Middle Tier Role Collect Amalga Query Processor\Query Processor Stored Queries Per Second
  Performance Collection: Amalga Query Processor\Query Processor Total Stored Queries onEssentialMonitoring Amalga 2009 Middle Tier Role Collect Amalga Query Processor\Query Processor Total Stored Queries
  Performance Collection: Amalga Script Engine\Commits Failed onEssentialMonitoring Amalga 2009 Script Engine Package Records the total number of transactions that failed during the database commit operation.
  Performance Collection: Amalga Script Engine\Commits Successful onEssentialMonitoring Amalga 2009 Script Engine Package Records the total number of transactions that were successfully committed to the database.
  Performance Collection: Amalga Script Engine\Messages Received onEssentialMonitoring Amalga 2009 Script Engine Package Records the number of messages received by the script engine.
  Performance Collection: Amalga Script Engine\Messages Received Per Second onEssentialMonitoring Amalga 2009 Script Engine Package Records the rate at which the parser is receiving messages for the current package.
  Performance Collection: Amalga Script Engine\Messages Retried onEssentialMonitoring Amalga 2009 Script Engine Package Records the total number of messages that were retried after an attempt to process them failed.
  Performance Collection: Amalga Script Engine\Messages Skipped onEssentialMonitoring Amalga 2009 Script Engine Package Records the total number of messages that were ignored after an attempt to process them failed. Note that this counter is only enabled if Amalga Script Engine error handling is configured to skip messages on failure.
  Performance Collection: Amalga Script Engine\Messages Successful onEssentialMonitoring Amalga 2009 Script Engine Package Records the total number of messages successfully processed for the current package.
  Performance Collection: Amalga Script Engine\Messages Unsuccessful onEssentialMonitoring Amalga 2009 Script Engine Package Records the total number of messages that failed during processing of the current package.
  Performance Collection: Amalga Script Engine\Multi-Connection Parser Writes onEssentialMonitoring Amalga 2009 Script Engine Package Records the total number of SQL writes executing under a commit transaction that failed while being written to the database. The SQL operations might be retried and subsequently succeed.
  Performance Collection: Amalga Script Engine\Package Stopped onEssentialMonitoring Amalga 2009 Script Engine Package Records the total number of times the current package was stopped because message-processing failed.
  Performance Collection: Amalga Script Engine\Partial Database Writes Failed onEssentialMonitoring Amalga 2009 Script Engine Package The total number of SQL writes (executing under a commit transaction) that failed while being written to the database.
  Performance Collection: Amalga Script Engine\Partial Database Writes Succeeded onEssentialMonitoring Amalga 2009 Script Engine Package Records the total number of SQL writes executing under a commit transaction that were successfully written to the database.
  SCOM payload was rejected onEssentialMonitoring Amalga 2009 Server Seed (at agent) SCOM payload was rejected
  SQL Replication 14151 alerting rule onEssentialMonitoring SQL DB Engine Raise an alert when SQL Server replication 14151 events occur. This event is not currently captured by SQL Server management packs and has impact on Amalga deployments.
  SQL Replication 14151 collection rule onEssentialMonitoring SQL DB Engine Collects SQL Server replication 14151 events. This event is not currently captured by SQL Server management packs and has impact on Amalga deployments.
  Update Cluster State Rule onEssentialMonitoring Amalga Physical Server This rule runs on Amalga servers and tracks the state of MSCS clusters (active or passive) and is required to run. It supports all cluster-aware Amalga monitors.

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