C&U Rollups and Real Time Vcenter metrics



I have been looking around but could not find a definite answer : What data range is used to produce the hourly and daily data points ?

To my understanding (from the documentation and ManageIQ posts I could find), an hourly data point is built by adding the data points of the following 60 minutes. For the 4:00 data point, it would mean that it was merged from any collection from 4:00 to 4:59.

What about daily points ? Providing the previous statement was correct, it would be 00:00 to 23:00 data points merged ?

Can someone correct this ? Without this information, an hourly timestamp from reports or utilization graphs is hard to understand.

The second interrogation is the Real Time metrics available for the Vcenter provider. Are they also collected every (by default) 10mins, like the other C&U data ?
This would mean that alerts based on Real Time metrics could be delayed by at most 10min, if I don’t change the default collection period.



About the Real Time metrics, I found this post

So there is this field ‘performance_collection_interval’ that sets an independant collection interval for alerts.

I guess I did not search wel enough !


Hi @Lux
May be this guide can help you: https://access.redhat.com/documentation/en-us/reference_architectures/2017/html/deploying_cloudforms_at_scale/

Try this chapter: https://access.redhat.com/documentation/en-us/reference_architectures/2017/html/deploying_cloudforms_at_scale/capacity_and_utilization#data_processing

Full chapter for C&U: https://access.redhat.com/documentation/en-us/reference_architectures/2017/html/deploying_cloudforms_at_scale/capacity_and_utilization

For timing of coordination see the following table:


And you can investigate metric_* tables to understand how things done.


Hi @igortiunov

Thank you for your answer, I was only looking at the product documentation, but this ‘reference architecture’ section seems very rich.


Yes, another useful guide by Peter McGowan. This guide have answers to many questions about CFME.