Date: Fri, 29 Mar 2024 05:39:25 +0000 (UTC) Message-ID: <1888948864.5611.1711690765115@ip-10-0-1-161.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5610_498420124.1711690765110" ------=_Part_5610_498420124.1711690765110 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
There are three main conceptual components to integrated = virtual and physical monitoring:
In addition to understanding these concepts, it is import= ant that you also understand the way other up.time functions change in a VMware vSphere monitoring context.
The core of integrated monitoring is up.time =E2=80=99s vSync, whose key functions are replicating metric= s and mirroring topologies, from VMware vSphere to up= .time .
vSync takes performance metrics gathered by VMware vSpher= e, normally for use in VMware tools such as the vSphere Client, and represe= nts them in up.time . VMware vSphere metrics tha= t are available in up.time include performance d= ata for VMs, the ESX servers that host them, and the VMware vCenter servers= that manage your configurations (including but not limited to datacenters,= clusters, and resource pools).
vSync also regularly monitors your VMware vSphere datacen= ter=E2=80=99s dynamic environment (including both physical and virtual asse= ts), ensuring the VMware vSphere inventory that up.ti= me is using for monitoring and reporting is always current. For more i= nformation, see Managing vSync= .
Some VMware vSphere components that act as logical groupi= ngs, including datacenters, clusters, resource pools, and vApps, are hierar= chically mirrored in up.time =E2=80=99s My Infrastructure inventory, and are represented th= rough their reported resource metrics. On the other hand, VMware vSphere co= mponents that are actual hosts, whether virtual or physical (i.e., a VMware= vCenter server, its component ESX servers,or their respective VMs) are rep= resented in up.time as Elements.
When you add a VMware vCenter server as an Element, all o= f the VMware vSphere components, whether organizational or compute resource= s, as defined through the vSphere Client, are imported to up.time , and their VMware-vSphere-collected metric data is migra= ted to the up.time DataStore. Additionally, all = ESX servers and VMs also become Elements.
There will be cases where administrators will want to act= ively manage which ESX server Elements (and subsequently, which VMs) are mo= nitored by up.time . For example, licensing cons= traints may prevent you from monitoring every ESX server in up.time , or the performance of particular portions of your vir= tual infrastructure may not be considered mission critical, and demand the = same level of uptime.
In these cases, administrators can include or exclude spe= cific up.time Elements from being monitored. Exc= lusions can be made on a per-VM basis, or by a logical grouping at the VMwa= re vSphere level (e.g., by cluster).
Any VMware vCenter component is by default represented in= My Infrastructure as either a known host o= r a known VM, and is grouped as such in the inventory. (By default, the My Inventory group names are Discovered Hosts and Discovered V= M Hosts ). When Elements are ignored, they are removed from My Infrastructure . If new hosts or VMs are discover= ed during vSync, they are added to the appropriate My Infrastructure group.
For more information, see Managing vCente= r Inventories in up.time.
When a VMware vCenter server is added to up.time , the hierarchical structure of its components is retain= ed (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 defined in up.time . = (See Topological Dependencies for more information.)=
When you define a physical topology or VMware vSphere top= ology in a Topological Dependency, the following behaviors are commonly obs= erved:
However, there are behaviors unique to Topological Depend= encies based on a VMware vSphere topology:
When you first add a VMware vCenter server to up.time as an Element, all of its managed ESX hosts and V= Ms are automatically added to up.time =E2=80=99s= monitored inventory. Each of these Elements is configured to sync its disp= lay name and host name with values used with the VMware vSphere Client. The= display name is mapped to the ESX host or VM object name in the VMware vSp= here Client, and the host name is mapped to its DNS name. During vSync, any= naming changes in vSphere are migrated to up.time Elements, and as such these names are by default not editable in up.time .
If desired, you can manually disable display name and hos= t name syncing with individual ESX hosts or VMs, and enter a name that will= be used in up.time , regardless of what it is o= n the network or in the VMware vSphere Client. See ESX Server Element Profiles or VM Element Profiles for more information.
Note that when a VMware vCenter server is added to up.time , and there are ESX hosts and VMs that are alr= eady part of the up.time inventory, these pre-ex= isting Elements=E2=80=99 display names and host names are not synced with v= Sphere. After adding a VMware vCenter server, if you would like all ESX hos= t and VM names to be updated through vSync, you will have to manually enabl= e the name sync options for each of these Elements.
In up.time , vSphere service g= roups exist to allow you to group similar Elements to perform common host c= hecks, not unlike groupings created in the vSphere Client (e.g., a cluster = or datacenter). The key difference with vSphere service groups from regular= ones is once established, vSphere service groups will be managed by the vS= ync process. Any changes detected with the VMware vCenter server=E2=80=99s = topology will automatically be reflected in the up.ti= me service group.
For information on creating a service group, see Creating Service Groups.
As one of vSync=E2=80=99s main benefits is to enable you = to combine virtual and physical monitoring, the following up.time tools are available assist with VMware vSphere analysis a= nd reporting.
Service Monitors consist of the following:
Diagnosis graphs consist of the following:
Reports consist of the following: