Reply to Message

View discussion in a popup

Replying to:
saholton
Contributor
Contributor

Thank you for the response - however,

The fix states "... the statistics collection level in vCenter Server must be set to 3 or above. However, this is not recommended in a production environment. Therefore, to obtain split the disk and network utilization data, you must run the Update Performance Counter utility one time on the vCenter Server machine...".


As stats L3 is not recommended for production (as stated in the "fix"), and as we should - instead of setting stats to L3 -  run this "fix", I assume (perhaps incorrectly??) that this fix does not implement a "full on" L3 stats environment, but some lesser collection environment that captures (perhaps only)

separate reads and writes in addition to/instead of the aggregates. 


Also, it is not clear if this fix collects (whatever extra stats it collects) for only the 5 min interval, trusting the stats replication to capture them before they evaporate in VC, or if these stats will then be propagated to all retention periods (1 hour, day, etc.). 


Also, IFF this is not a "full on" L3, it is still difficult to determine what effects this will have on the VC database, as the "tool" is not (that I can find) set up to calculate "partial" L3 stats collection for some unknown retentions.

Reply
0 Kudos