Introduction This document describes the best practices and recommendations for VMware vRealize Operations Manager. This document is not an installation guide, but a guide that supplements the vRealize Operations Manager installation and documentation available in the v realize There are additional best practices outlined in the product documentation, therefore, existing information may not be displayed in this document. Please refer to the product documentation for additional best practices This information is for the following products and versions. PRODUCT VERSION DOCUMENTATION vRealize Operations Manager.6,6.7,7.0 https://docs.vmware.com/en/vrealize-operations-manager/index.html Best Practices Concepts This document provides information based on development, test, field, and customer interaction. Each environment is unique and the way vRealize Operations Manager is used may vary; hence, this information provides general principles or techniques that, when applied, will produce results that are superior to those achieved by other means or by standar n certain cases, it may not be practical to apply best practice methods nor is there a requirement to use all best practices available. The area of best practice should be applied appropriately based on the environment, the user and the way that rEalize Operations Manager is being used Following are the advantages of applying best practices with rEalize Operations Manager Proven results insistency · Greater Stability Areas of Best Practices Applying best practices for vRealize Operations Manager focuses on three key areas: · Platform( product The technical portion of the product, which includes architecture and sizing, deployment, cluster, high availability, emote collector, APl, interoperability and integration, backup& restore, and disaster recovery · Content(product The functional part of the product, meaning the content that""sits on"the platform. Content includes policies, dashboards, alerts, reports, super metrics, groups, and actions The how you use the product in your operations. This includes working with other roles in Operations(e.g. NOC Storage, and Management). Examples of Operations are processes, roles, groups, tenants vRealize Operations Manager Best Practices/5vRealize Operations Manager Best Practices /5 Introduction This document describes the best practices and recommendations for VMware vRealize Operations Manager. This document is not an installation guide, but a guide that supplements the vRealize Operations Manager installation and configuration documentation available in the vRealize Operations Manager Documentation Center. There are additional best practices outlined in the product documentation; therefore, existing information may not be displayed in this document. Please refer to the product documentation for additional best practices. This information is for the following products and versions. PRODUCT VERSION DOCUMENTATION vRealize Operations Manager 6.6, 6.7, 7.0 https://docs.vmware.com/en/vRealize-Operations-Manager/index.html Best Practices Concepts This document provides information based on development, test, field, and customer interaction. Each environment is unique and the way vRealize Operations Manager is used may vary; hence, this information provides general principles or techniques that, when applied, will produce results that are superior to those achieved by other means or by standard use. In certain cases, it may not be practical to apply best practice methods nor is there a requirement to use all best practices available. The area of best practice should be applied appropriately based on the environment, the user and the way that vRealize Operations Manager is being used. Following are the advantages of applying best practices with vRealize Operations Manager: • Proven Results • Consistency • Enhanced Performance • Improved usability • Greater Stability Areas of Best Practices Applying best practices for vRealize Operations Manager focuses on three key areas: • Platform (product) The technical portion of the product, which includes architecture and sizing, deployment, cluster, high availability, remote collector, API, interoperability and integration, backup & restore, and disaster recovery. • Content (product) The functional part of the product, meaning the content that “sits on” the platform. Content includes policies, dashboards, alerts, reports, super metrics, groups, and actions. • Operations The how you use the product in your operations. This includes working with other roles in Operations (e.g. NOC, Storage, and Management). Examples of Operations are processes, roles, groups, tenants