Monday, August 21, 2017

Demystifying vRealize Operations Data Collection

Around 3 years ago I wrote an article explaining the data collection process of vRealize Operations Manager. In that article, I wrote about the path followed by the data from source to destination. Fast forward 3 years and I still get questions about vROps data collection process and granularity.

People have different notions about this, so let me share the secret sauce:

vRealize Operations Manager Out of the Box, is configured to collect data every 5 (FIVE) minutes form the source. The collector wakes up every 5 minutes and gets last 15 samples of 20 seconds interval from the source.


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


Once the 20 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 vROps. In parallel, operations such as threshold checking, computed metric calculation etc. take place.

As we all know 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 infact 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.

Also, it is possible to change this default collection cycle from 5 minutes 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 processinh.

Hope this helps!!




2 comments:

  1. Hello,

    Thanks for the Article.

    But I am confused about the Statement that the collection cycle can set to 1 minute.

    I tried that for specific vSphere Object without success.
    See also:
    https://communities.vmware.com/thread/565824

    Best regards
    Markus

    ReplyDelete
    Replies
    1. I tested that in my vROps environment running 6.6 and I was able to default all objects int he adapter to 1 minutes without any issues. I will look at the community article.

      Delete