Health Service recommended configuration monitor
This monitor tracks the configuration of the Ops Mgr Health Service, when it runs on a server where the Veeam Collector is installed.
The monitor is enabled by default. You can override the following parameters:
Name | Default Value | Description |
PersistenceCacheMaximum | 262144 | Specifies a threshold for the 'PersistenceCacheMaximum' registry setting. If the value is below the threshold, the monitor will start generating alerts. |
PersistenceCheckpointDepthMaximum | 104857600 | Specifies a threshold for the 'PersistenceCheckpointDepthMaximum' registry setting. If the value is below the threshold, the monitor will start generating alerts. |
PersistenceVersionStoreMaximum | 131072 | Specifies a threshold for the 'PersistenceVersionStoreMaximum' registry setting. If the value is below the threshold, the monitor will start generating alerts. |
StateQueueItems | 20480 | Specifies a threshold for the 'StateQueueItems' registry setting. If the value is below the threshold, the monitor will start generating alerts. |
MaximumQueueSizeKb | 204800 | Specifies a threshold for the 'MaximumQueueSizeKb' registry setting. If the value is below the threshold, the monitor will start generating alerts. |
Note: If you have configured several overrides of the same type, select the Enforced check box for an override that should have priority over all other overrides.
The Veeam Collector publishes large amounts of data concerning the monitored VMware vSphere environment. For this reason some specific configuration and optimization of the local Ops Mgr Health Service is required, so that the Health Service can process this data load efficiently. These configuration changes are part of the registry settings for the Ops Mgr Health Service.
There are two possible situations where this alert will fire:
Ops Mgr Agent. If an Ops Mgr agent is used to host the Veeam Collector service, then no action is required. This monitor will automatically run a Recovery Action which will make the required registry changes, and then restart the Health Service in order to apply the configuration. The alert will then automatically close.
Ops Mgr Management server. If a Management Server is used to host the Veeam Collector role, then the monitor will not automatically restart the Health Service. This is by design, to avoid impact to other monitoring tasks which a Management Server may be performing.To resolve the alert for a Management Server, run the Recovery Action manually. This is available either via the Health Explorer for this monitor, or in the Tasks pane.Once the Task is run and the service restarted, the alert will automatically close.
Use the Alerts View to see all current open issues for this object. Use the Events View to review any error and warning events for this object. Open a Performance View to see the performance metrics for this object and all contained objects. Open a Diagram View to analyze the relationships of this object to other components.
See the Help Center for more information including reference lists of all Rules and Monitors and full set of User Guides for the Veeam MP for VMware.
See the VMware Online Documentation for more information on VMware vSphere, in particular:
| Target | Veeam.Virt.Extensions.VMware.Collector | ||
| Parent Monitor | System.Health.ConfigurationState | ||
| Category | ConfigurationHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Low | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Veeam.Virt.Extensions.VMware.HealthServiceRegistry.MonitorType | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
<UnitMonitor ID="Veeam.Virt.Extensions.VMware.HealthService.Monitor.RegistryConfiguration" Accessibility="Public" Enabled="onEssentialMonitoring" Target="Veeam.Virt.Extensions.VMware.Collector" ParentMonitorID="SystemHealth!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="Veeam.Virt.Extensions.VMware.HealthServiceRegistry.MonitorType" ConfirmDelivery="true">
<Category>ConfigurationHealth</Category>
<AlertSettings AlertMessage="Veeam.Virt.Extensions.VMware.HealthService.Monitor.RegistryConfiguration_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Low</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Green" MonitorTypeStateID="Ok" HealthState="Success"/>
<OperationalState ID="Yellow" MonitorTypeStateID="NotOk" HealthState="Warning"/>
</OperationalStates>
<Configuration>
<PersistenceCacheMaximum>262144</PersistenceCacheMaximum>
<PersistenceCheckpointDepthMaximum>104857600</PersistenceCheckpointDepthMaximum>
<PersistenceVersionStoreMaximum>131072</PersistenceVersionStoreMaximum>
<StateQueueItems>20480</StateQueueItems>
<MaximumQueueSizeKb>204800</MaximumQueueSizeKb>
<Frequency>86400</Frequency>
<MGName>$Target/ManagementGroup/Name$</MGName>
</Configuration>
</UnitMonitor>