Maintenance schedules prevent vRealize Operations Manager from showing misleading data from resources that are offline or in other unusual states because of maintenance.

Many resources in the enterprise might be intentionally taken offline. For example, a server might be deactivated to update software. If vRealize Operations Manager collects metrics when a resource is offline, it might generate incorrect anomalies and alerts that affect the data for setting dynamic thresholds for the resource attributes. When a resource is identified as being in maintenance mode, vRealize Operations Manager does not collect metrics from the resource or generate anomalies or alerts for it.

If a resource undergoes maintenance at fixed intervals, you can create a maintenance schedule and assign it to the resource. For example, you can put a resource in maintenance mode from midnight until 3 a.m. each Tuesday night. You can also manually put a resource in maintenance mode, either indefinitely or for a specified period of time. These methods are not mutually exclusive. You can manually put a resource in maintenance mode, or take it out of maintenance mode, even it if has an assigned maintenance schedule