Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vRealize Operations Data Collection (67792)

Last Updated: 1/30/2023Categories: InformationalTotal Views: 21675Language:
Chinese (Simplified)English

17 like this article

Subscribe to get an email
newsletter with new updates

17 people found this helpful Please provide article feedback:

Details

This article serves to explain the process of a standard vRealize Operations data collection, and how it arrives at a value for a data point.

The below mostly pertains to the VMware vSphere solution and may differ for other solutions.

Solution

vRealize Operations out of the box, is configured to collect data every 5 minutes from the source.
For vCenter performance counters, the collector wakes up every 5 minutes and gets the last 15 samples of 20 seconds interval from the source.

15 Data Points X 20 Seconds = 300 Seconds ( 5 minute collection cycle)

Once the 15 samples are in, we go ahead and average them out to come up with the value which is saved in the FSDB (File System Database) of vRealize Operations.
In parallel, operations such as threshold checking, computed metric calculation etc. take place.

You can further transform this data in views and super metrics by using functions such as Min, Max, Standard Deviation etc
All these functions run on the data saved in FSDB which is the 5 minute data point explained above.

These transformations are not ran on the 20 seconds samples.
The 20 seconds samples in fact are used to do calculations of the 5 minutes data points and are dropped as soon as that calculation is done. This reduces the storage requirement drastically.

Note: It is possible to change this default collection cycle from 5 minutes all the way down to 1 minute, however it is not recommended to do that unless you understand the overall impact on Compute and Storage for increased collection and processing.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
ESXi/ESX ホストのネットワーク カードが検出されない (1034782)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Operations Manager

VMware vRealize Operations

Related Versions:

Take Our Survey

Support Assistant