Child pages
  • vCenter Configuration Mirroring
Skip to end of metadata
Go to start of metadata

vCenter Configuration Mirroring

In order for Uptime Infrastructure Monitor to successfully integrate virtual and physical monitoring, it needs to be completely in step with a highly dynamic virtual infrastructure. For administrators, understanding the level at which Uptime Infrastructure Monitor mirrors changes helps you figure out what you can integrate into an alerting policy, and how to avoid false positives.

vSync Change Events

The following VMware vCenter event types are detectable by vSync, along with the action performed in Uptime Infrastructure Monitor:

Datacenters

datacenter found

  • automatically added to any vSphere service groups that have a master datacenter service that unconditionally takes newly discovered datacenters as child services
  • association is established with a VMware vCenter server

datacenter deleted

all references to the datacenter are removed from Uptime Infrastructure Monitor

ESX Servers

host found

  • automatically added to any vSphere service groups that have a master ESX host service that unconditionally takes newly discovered ESX hosts as child services
  • association is established with a VMware vCenter server
  • automatically moved to the list of ignored Elements for a VMware vCenter server if its addition violates your license

host deleted

  • monitoring is disabled, and automatically switched to list of ignored Elements for a VMware vCenter server
  • all references to the ESX server in Uptime Infrastructure Monitor are removed

power state change

all regular procedures associated with power state changes are performed

host added to or removed from cluster

VMware vCenter server topology is updated

configuration change

configuration details are reflected in the host’s Uptime Infrastructure Monitor profile, unless it is on the list of ignored Elements

display name change

a change to the ESX host's display name in the VMware vSphere Client is reflected in the host’s Uptime Infrastructure Monitor Element display name, unless it is on the list of ignored Elements

host name change

a change to the ESX host's DNS name is reflected in the host’s Uptime Infrastructure Monitor Element host name, unless it is on the list of ignored Elements

VMs

VM licensing change

VMs do not affect Uptime Infrastructure Monitor licensing if they are managed by an ESX server monitored by Uptime Infrastructure Monitor

VM found

  • automatically added to any vSphere service groups that have a master VM service that unconditionally takes newly discovered VMs as child services
  • association is established with an ESX server

VM deleted

  • monitoring is disabled, and automatically switched to list of ignored Elements for a VMware vCenter server
  • all references to the VM in Uptime Infrastructure Monitor are removed

power state change

all regular procedures associated with power state changes are performed

VM vMotion

automatically update topological dependencies to reflect the new host for the VM, and the previous one

configuration change

configuration details are reflected in VM’s Uptime Infrastructure Monitor profile unless it is on the list of ignored Elements

display name change

a change to the VM’s display name in the VMware vSphere Client is reflected in the VM’s Uptime Infrastructure Monitor Element display name, unless it is on the list of ignored Elements

host name change

a change to the VM’s DNS name is reflected in the VM’s Uptime Infrastructure Monitor Element host name, unless it is on the list of ignored Elements

vApps

vApp found

  • automatically added to any vSphere service groups that have a master vApp that unconditionally takes newly discovered vApps as child services
  • association is established with a VMware vCenter server

vApp deleted

  • automatically removed from the hierarchical listing in My Infrastructure
  • all service monitor references to the VMware vCenter are removed

power state change

all regular procedures associated with power state changes are performed

configuration change

configuration details reflected in vApp’s Uptime Infrastructure Monitor profile

Clusters

cluster found

  • automatically added to any vSphere service groups that have a master cluster service that unconditionally takes newly discovered clusters as child services
  • association is established with a VMware vCenter server
  • automatically moved to the list of ignored Elements for a VMware vCenter server if its addition violates your license

cluster deleted

  • automatically removed from the hierarchical listing in My Infrastructure
  • all service monitor references to the VMware vCenter are removed

configuration change

configuration details reflected in cluster’s Uptime Infrastructure Monitor profile

Resource Pools

resource pool found

  • automatically added to any vSphere service groups that have a master resource pool that unconditionally takes newly discovered resource pools as child services
  • association is established with a VMware vCenter server

resource pool deleted

  • automatically removed from the hierarchical listing in My Infrastructure
  • all service monitor references to the VMware vCenter are removed

configuration change

configuration details reflected in resource pool’s Uptime Infrastructure Monitor profile

  • No labels