...
vSphere Components and Topological Dependencies
When a VMware vCenter server is added to up.time, the hierarchical structure of its components is retained (and used in My Infrastructure ). up.time observes particular monitoring rules to these existing VMware vSphere topologies that supplement the behavior of physical topologies that have been are defined in up.time. (See Topological Dependencies for more information.)
When you define a physical topology or VMware vSphere topology in a Topological Dependency, the following behaviors are commonly observed:
- if a topological parent is experiencing downtime, the child Elements in the topology will share the status (i.e., an Element's dependencies will automatically switch to its status)
- an outage with an Element, whether actual or topological, will initiate a host check on its parent (e.g., a service monitor and its host, or a host and its topological parent)
However, there are behaviors unique to Topological Dependencies based on a VMware vSphere topology:
- as VMs migrate, their links to their ESX hosts is maintained
- up.time will be aware of power states in the virtual infrastructure, such that parent Elements that are powered down will not spawn alerts with its child Elements (e.g., all of a VMware vCenter servers many ESX servers and VMs)
...