Analysis paradigm

The health of the discovered applications (VoipApplications), network services (VoipNetworkServices), and processes (VoipProcesses) is central to the root-cause analysis of a VoIP system. Failed services (applications, network services) impact many aspects of a VoIP system, including Call Manager groups (redundancy groups) and Call Manager clusters.

A service (application, network service) may run as a single process or as multiple processes. For a single-process service, VoIP Availability Manager discovers and monitors the service as a single process. Every single-process service is deemed “critical.”

For a multiple-process service, VoIP Availability Manager discovers and monitors the service by discovering and monitoring the processes executing as part of the service.

• Some of the processes are deemed “critical” because they are considered more important to the health of the service than others.

• Other processes are deemed “key” because one down key process will bring down the entire application. A process is defined as key during the certification process.

• Others are deemed “non-critical” because they are less important to the health of the service or application.

  The state of a critical or a key process has more importance in correlation analysis than the state of a non-critical process.

  For a discovered multiple-process service, VoIP Availability Manager also creates a ComposedOf relationship between the service and each of its processes, to identify the dependency of the service on its component processes.