The global settings determine how vRealize Operations retains data, keeps connection sessions open, and other settings. These are system settings that affect all users. Some of these settings are not editable. The global settings are grouped into four types. .
Settings in the Data Retention Category
Number of days to retain the recent task data for actions.
The data is purged from the system after the specified number of days.
Number of hours to retain objects that are deleted from an adapter data source or server before deleting them from vRealize Operations.
An object deleted from an adapter data source is identified by vRealize Operations as not existing and vRealize Operations can no longer collect data about the object. Whether vRealize Operations identifies deleted objects as not existing depends on the adapter. This feature is not implemented in some adapters.
For example, if the retention time is 360 hours and a virtual machine is deleted from a vCenter Server instance, the virtual machine remains as an object in vRealize Operations for 15 days before it is deleted.
This setting applies to objects deleted from the data source or server, not to any objects you delete from vRealize Operations on the Inventory page.
A value of -1 deletes objects immediately.
You can define the number of hours per object type to retain objects that no longer exist and check for object type overrides. To add individual object types and set up their values, click the Object Deletion Scheduling icon. You can also edit or delete these object types.
|Deletion Scheduling Interval||24 hours||
Determines the frequency to schedule deletion of resources. This setting works with the Deleted Objects setting to remove objects that no longer exist in the environment. vRealize Operations transparently marks objects for removal that have not existed for the length of time specified under Deleted Objects. vRealize Operations then removes the marked objects at the frequency specified under Deletion Scheduling Interval.
Number of days to retain the history of the object configuration, relationship, and property data.
The configuration data is the collected data from the monitored objects on which the metrics are based. The collected data includes changes to the configuration of the object.
The data is purged from the system after the specified number of days.
|Generated Reports Retention||
Number of days to retain generated reports. If disabled, all the generated reports will be retained.
The minimum number of days you can set is one and the maximum number of days you can set is 3600.
Number of days to retain canceled alerts and symptoms.
The alerts and symptoms are either canceled by the system or by a user.
|Time Series Data Retention||
Number of months that you want to retain the collected and calculated metric data for the monitored objects. This setting is set to 6 months by default for 5 minutes interval data retention.
|Additional Time Series Retention||
The number of months that the roll-up data extends beyond the regular period. The roll-up data is available starting from the end of the regular period and until the end of the roll-up data retention period. If you specify 0 as the value, then this will effectively disable the Additional Time Series Data Retention time and only data specified in Time Series Retention is stored. This setting ensures that after 6 months of normal retention for 5 minutes, the seventh month data is rolled up into a one Hour roll up. You can set up this option up to 120 months for data roll ups.
|Deleted Users||100 days||
You can specify the number of days to keep custom content created by a user who has been removed from vRealize Operations or by the automatic synchronization of LDAP. For example, the custom dashboards created by a user.
|External Event Based Active Symptoms||disabled||
The number of days to retain the external event-based active symptoms.
|Maintain Relationship History||disabled||
You can maintain a history of all the relationships of all the monitored objects in vRealize Operations.
Settings in the Cost/Price Category
|Cost Calculation||enabled||The host time at which cost calculations are run.|
|Currency||You can specify the currency unit that is used for all the cost calculations. You can select the type of currency from the list of currency types by clicking Choose Currency. From the Set Currency, select the required currency and confirm your action by clicking the check box, and set the currency.|
|Cluster Utilization Ceiling Factor||5||Ceiling for Expected Utilization when running on Actual Utilization.|
|Orphaned Disks Collection||8:00 PM||Host time to collect orphaned disks.|
|Tag Based Costing Metrics||Disabled||When enabled, vRealize Operations additional cost metrics per tag.|
|Tag Based Pricing Metrics||Disabled||When enabled, vRealize Operations additional pricing metrics per tag.|
Settings in the User Access Category
|Allow vCenter users to log in to individual vCenters from vRealize Operations||enabled||Allows vCenter users to log in to individual vCenters using the vRealize Operations UI.|
|Allow vCenter users to log in from vCenter clients||enabled||Allows vCenter users to log in from vCenter clients.|
|Allow vCenter users to log in to all vCenters using the vRealize Operations UI||enabled||Allows concurrent UI login sessions per user. Once changed, this setting affects the subsequent login sessions.|
|Concurrent UI login sessions||enabled||Allows concurrent UI login sessions per user. Once changed, this setting affects the subsequent login sessions.|
|Allow non-imported vIDM user access||Allows non-imported VMware Identity Manager users to be created automatically as read-only users upon first access. If disabled, only VMware Identity Manager imported users or users belonging to imported VMware Identity Manager groups will be granted access.|
Settings in the System Settings Category
|Session Timeout||30 minutes||
If your connection to vRealize Operations is idle for the specified amount of time, you are logged out of the application.
You must provide credentials to log back in.
|Dynamic Threshold Calculation||enabled||
Determines whether to calculate normal levels of threshold violation for all objects.
If the setting is disabled, the following area of vRealize Operations does not work or are not displayed:
Disable this setting only if you have no alternative options for managing resource constraints for your vRealize Operations system.
|Customer Experience Improvement Program||enabled||
Determines whether to participate in the Customer Experience Improvement Program by having vRealize Operations send anonymous usage data to https://vmware.com.
|System access URL||You can specify the URL that is used to access the system when a load balancer is used. The URL that you enter here is displayed in the outbound notifications and while sharing dashboards. The IP /FQDN of the URL is used to register the vCenter Server when you configure the vCenter Server cloud account.|
Determines whether to allow vRealize Operations to automate actions. When an alert triggered, the alert provides recommendations for remediation. You can automate an action to remediate an alert when the recommendation is the first priority for that alert. You enable actionable alerts in your policies.
|Enable Standard Certificate Validation||disabled||
This option enables certificate verification to Test Connection in the Create or Modify AI screen, using a standard verification flow.
The option checks CA authority.
|Threshold For Adapters Certificate Expiration Alert||
5 for critical
14 for immediate
30 for warning
|Set the number of days before which the system must raise certification expiration alerts.
To change the values of Critical, Immediate and Warning alerts, click the corresponding icon and move them along the slider. Alternatively, set the values manually.
Click Save after you make your changes.
Note: For critical alerts, an alert banner is displayed under on the day of certification expiry. For example, if the critical alert is set to 10, then on the 10th day, an alert banner is displayed in the Home page.