Amalga 2009 DADE Service - Receiver Class

  • ID:  Microsoft.Amalga.UIS.2009.DADEServiceHost_Receiver
  • Description:   
  • Class Hierarchy: 
    Object
    Configuration Item
    Logical Entity
    Application Component
    Windows Application Component
    Amalga Application Component
    Amalga Windows Service
    Amalga 2009 Windows Service
    Amalga 2009 DADE Windows Service
    Amalga 2009 DADE Service - Receiver

  • Attributes:  Public, Non-Hosted
Login
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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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) Generates an alert when a DADE Filer service has 1 or more messages in its Error folder. 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) This monitor alerts when at least 1 message has not been received/processed within X minutes (X may be fixed or schedule dependent). Monitor DADE Filer count of pending files appears to be backlogging Generates an alert when a DADE Receiver service has 1 or more messages in its Error folder. 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) This monitor alerts when at least 1 message has not been received/processed within X minutes (X may be fixed or schedule dependent). This monitor is meant to alert customers of a known issue with the DADE. See product knowledge for details on this monitor. DADE Retriever - count of pending files for outbox folder appears to be backlogging Amalga 2009 DADE Service - Receiver Amalga 2009 Services Group Amalga 2009 DADE Service - Deleter (node) Amalga 2009 DADE Service - Filer (node) Amalga 2009 DADE Service - Receiver (node) Amalga 2009 DADE Service - Retriever (node) Amalga 2009 DADE Service - Sender (node) Amalga 2009 Middle Tier Windows Service Amalga 2009 Script Engine Service Node

Download diagram as a Visio file

Properties

Display Name Description
Agent Name  
Asset Status Asset status
Class Name  
Cluster Name  
Display Name Display name of the object.
Environment (Key)  
Event Log Name  
Event Source Name  
Is Clustered Service (Key)  
Notes Notes
Object Status Object status
Possible Owner Count Count of possible owner nodes if this service is clustered
Resource Group Name  
Service Instance Name (Key)  
Service Type (Key)  
VIP Name (Key)  

Discovered By

There are no discoverys discovered this class.

Relations

Health Source
NameClassType
Amalga 2009 Windows Service contains Amalga2009 Windows Service Node Amalga 2009 Windows Service Membership
Owned By User Configuration Item Reference
Affects Customers Configuration Item Reference
Serviced By User Configuration Item Reference
Contains Configuration Item Configuration Item Membership
Is Related to Configuration Item Configuration Item Reference
Config Item References Location Configuration Item Reference
Entity Watched By Perspective Object Reference

Health Target
NameClassType
Amalga 2009 Services Group contains Amalga 2009 DADE Service - Receiver Amalga 2009 DADE Service - Receiver Membership

Class Knowledgebase

Summary
This class does not contain any summary.
External References
This class does not contain any external references.

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