Back to Geneos FAQ

Netprobe consuming high CPU

This problem is related to the following:

• Netprobe’s CPU is high
• Netprobe is busy
• Netprobe is stale

Problem Copied

Your monitoring has detected a Netprobe process that is constantly consuming high CPU (80% and above) for a period of time.

Possible causes Copied

This is caused by the amount of data extracted by the plugins running on the said Netprobe. Plugins such as the FKM, State Tracker, Message Tracker, JMX, API, Toolkit and SQL-Toolkit can extract hundreds to thousands of data if they are not properly configured.

Possible solutions Copied

• Monitor by exception — see Managing Load in Geneos.

• Split the samplers into multiple Netprobes — this spreads the CPU utilization to multiple Netprobe processes. It also ensures that other samplers can sample immediately instead of waiting for heavy samplers to finish.