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

Health Service Handle Count Threshold Monitor

  • ID:  Microsoft.SystemCenter.Agent.HealthService.HandleCountThreshold
  • Description:  This monitor ensures that the "Process\Handle Count" counter for the "HealthService.exe" process does not exceed a set threshold over a series of consecutive samples. If the conditions are met, this monitor will change to a critical state, which will then roll up to the "Health Service State" monitor. The "Health Service State" monitor is configured to run a recovery when its state is critical, which will automatically attempt to restart the System Center Management Health Service.
  • Target:  Health Service
  • Enabled:  Yes

Operational States

Name State Description
Handle Count below threshold Success  
Handle Count exceeded threshold Error  

Overridable Parameters

Parameter Name Default Value Description Override
Agent Performance Monitor Type (Consecutive Samples) - Monitoring interval 120  
Agent Performance Monitor Type (Consecutive Samples) - Threshold 6000  
Agent Performance Monitor Type (Consecutive Samples) - Number of samples 5  

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This unit monitor measures the Process\Handle Count utilization for the Health Service process. If it exceeds the configured threshold, a recovery attempts to restart the System Center Management Health Service to ensure it doesn't continue to overwhelm the computer.

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

System Center Management Health Service Role

Handle Count Threshold

Agent

6,000

Management Server

10,000

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

System Center Management Health Service Role

Restart Recovery Behavior

Agent

Enabled

Management Server

Disabled

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, the System Center Management Health Service 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 System Center Management Health Service and it related process to consume more resources.

Resolutions

The default action for this monitor running on agents is to restart the System Center Management Health Service. Because this recovery is enabled by default on agents, no user action is required.

If you still see this monitor in a critical state, the System Center Management Health Service may not have restarted correctly or the action account this agent has been configured with does not have the right permissions to restart the service.

If this is the case, start the System Center Management Health Service windows service.

The hotfix provided in Knowledge Base article 968760 can correct some issues that result in this monitor changing to a critical state. Ensure that the hotfix from Knowledge Base article 968760 (http://go.microsoft.com/fwlink/?LinkId=196234) has been installed on any computers that are using too much memory.

External References
This monitor 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