Review and follow the general sizing guidelines.

  • Validate the sizing guidelines with your actual environment

    The sizing guidelines provide general estimates and requires confirmation with the actual environment. For example, the data entered in the sizing calculator may yield additional objects not captured in the actual environment or vice versa.

  • Calculate only the components which will be monitored

    It is possible that some components do not need to be monitored; therefore, exclude those components in the sizing calculations.

  • Size the Cluster

    There are multiple sizes for analytics nodes, extra small, small, medium, large and extra-large. It is best to use the least number of nodes when possible. For example, if the recommendation is to have 10 large nodes or 4 extra-large nodes, use the lesser number of nodes to minimize the amount of communication across more nodes.

  • Size the Remote Collectors

    There are two sizes for default remote collectors, standard and large. Use the appropriately sized remote collector based on how much data will be collected. If necessary, use multiple remote collectors to ensure the proper sizing of remote collectors for the environment.

  • Adjust the time series data retention to keep data for a timeline which data is critically needed

    The default setting for data retention is six months. If only three months of data is required, lower the default value. Understand what you gain when using longer data retention periods. It may not necessarily help having longer retention periods. Depending on your operational needs, configure the retention period to suit your requirements.

  • Consider additional storage and IO requirements for longer data retention

    For those times when longer data retention periods are required, consider additional storage and increased IO requirements. For example, retail businesses may need to keep more than one year of data to account for seasonal peaks.

  • Leverage the additional time series retention to keep longer historical data while minimizing the time series data retention period.

    The default setting for additional time series retention is thirty-six months. Adjust the default value to a necessary period and lower the time series data retention period to save on the amount of data being retained.

  • Add VMDK instead of extending

    Increase storage by adding a VMDK to minimize impact to existing

  • Only install Management Packs that are available on the VMware Solution Exchange

    There are several management packs available for vRealize Operations; however, only management packs certified and supported by VMware are available on the VMware Solution Exchange.

  • Confirm VMware product compatibility support before installing or upgrading components

    Refer to the VMware Product Interoperability Matrix for all VMware product and management packs supported with vRealize Operations.

  • Validate supported management packs created by VMware partners

    The 3rd party authored Management Packs that are supported are listed in the VMware Compatibility Guide.

  • Before adding Management Packs, verify the additional metrics they will provide

    The metric names may look correct but may not always mean what you really want. Be sure that the metrics from added management packs are what you really need and used properly; otherwise, disable the unnecessary metrics.