• Management Pack:  SCOM 2016
  • MP Version:  1.0
  • Released:  10/19/2018
  • Publisher:  Microsoft

(Deprecated) Monitoring Host Private Bytes Handle Count Rule

  • ID:  Microsoft.SystemCenter.ManagementServer.MonitoringHost.PrivateBytesThreshold
  • Description:  Restarts the Health service when the Monitoring Host process exceeds the Process\Private Bytes threshold.
  • Target:  Management Server
  • Enabled:  No

Overridable Parameters

Parameter Name Default Value Description Override
Frequency 120  
Priority 1  
Severity 2  
Threshold 1610612736  
Num Samples 5  

Run As Profiles

Name
Default

Alert Details

Message Priority Severity
Monitoring Host Private Bytes Threshold Alert Message (Management Server) Medium Critical

Rule Knowledgebase

Summary

This rule is disabled by default because it has been replaced by a monitor.

This rule measures the Process\Private Bytes utilization for all instances of the MonitoringHost.exe process. If it exceeds the configured threshold, an alert is generated.

There are different thresholds depending on the role that System Center Management Health Service configured to perform. The following summarizes the default thresholds:

System Center Management Health Service Role

Private Bytes Threshold

Agent

100 MB

Management Server

1,500 MB

Below is the configuration for the response that attempts to restart the System Center Management Health Service:

System Center Management Health Service Role

Restart Response Behavior

Agent

Enabled

Management Server

No restart response

Causes

A brief summary of potential causes are:

Too many rules and monitors are loaded from all the management packs this System Center Management Health Service has been configured with.

A misconfigured rule or monitor collecting too much data or processing too much data (e.g. performance counter collection rule collecting data every 1 second)

This can be caused by the System Center Management Health Service running many management packs. Each Management Pack may have a lot of monitoring that uses a small amount of resources. With many management packs that add up to many thousands of rules and monitors, each MonitoringHost.exe instance may start consuming more resources.

This may be expected for this System Center Management Health Service depending on the type of monitoring the System Center Management Health Service is performing.

Another cause could be one or more rules and monitors that are not conforming to some best practices. An example is a performance counter rule that attempts to collect performance data every 1 second. Too many rules or monitors configured this way will cause the monitoring host.exe process to consume more resources.

Resolutions

The default action for this rule running on Management Servers is to alert.

If you feel that the resource utilization is appropriate for the amount of monitoring being performed by this agent, you can override the threshold or disable the recovery.

If the System Center Management Health Service and its associated MonitoringHost.exe process are still consuming too many resources, you can restart the System Center Management Health Service windows service to mitigate this problem.

External References
This rule does not contain any external references.

See Also for SCOM 2016 Management Pack


Downloads for SCOM 2016 Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED