|SoftwareService (and all derived classes||MinorSymptom||This symptom aggregates high severity events that are externally instrumented.|
|MajorSymptom||This symptom aggregates medium severity events that are externally instrumented.|
|CriticalSymptom||This symptom aggregates high severity events that are externally instrumented on the SoftwareService class.|
|DownSymptom||This symptom indicates that this SoftwareService is down according to the external instrumentation received.|
|UnitaryComputerSyst em (and all derived classes)||Unresponsive||This symptom indicates that a system’s protocol endpoints are not responding to ICMP or SNMP polls and that connections to applications hosted by the system are down. Application Connectivity Monitor diagnoses the System Unresponsive problem when it receives an UnresponsiveSymptom from IP Availability Manager.|
|ResourceException||Indicates that the computer system is experiencing CPU or memory degradation; this is only received from the VMware Smart Assurance IP Server Performance Manager (source of this symptom).|
Table Application Connectivity Monitor correlation with imported events demonstrates how the symptomatic events from a third-party adapter are used in the correlation of Application Connectivity Monitor:
- The topology is a SoftwareService (Sw1) that is hosted by Host1.
- The symptomatic events marked with a bold “X” are the required event to diagnose the problem. For example, if Application Connectivity Monitor does not receive a DownSymptom for a SoftwareService, it will not diagnose SoftwareService Down.
Table 2. Application Connectivity Monitor correlation with imported events Problems Host 1 Unresponsive Host 1 ResourceException Sw1 Down Sw1 Malfunction Sw1 Degraded Symptoms
X X X
X X X X
X X X