Netprobe performance issues: samplers are not keeping up

Related topics Copied

Netprobe not sampling, Netprobe data is out of date, Netprobe not showing live data

Problem Copied

• Netprobe samplers are not running at the sampling interval
• Netprobe data shown in the Active Console is not up-to-date

Possible causes Copied

• One or more samplers are taking a long time to execute.
• Gateway may be busy and lagging behind in processing updates.

Possible solutions Copied

One or more samplers are taking a long time to execute Copied

This is typically a two-step process. As a first step, enable debug to find out how much time it takes for each sampler to run. This can be done by enabling the following debug setting on the Netprobe:

<probe name="Test Netprobe">
<hostname>Test Host</hostname>
**<debug>**
**<debug>**
**<module module="SAMPLING">**
**<setting>\*</setting>**
**</module>**
**</debug>**
**</debug>**
</probe>

Gateway Setup Editor Probe entry:

After the debug is applied and the issue occurs again, send us the complete Netprobe log so we may identify the problematic samplers and advise the next step.

Netprobe data shown in the Active Console is not up-to-date Copied

It is possible the Gateway is overloaded and lagging behind in processing the updates from the Netprobe. This could cause the Active Console to render old or stale data as if the Netprobe is not keeping up. To verify, check the Gateway log and look for persistent high max age value or entries like Detected stale data.

WARN: Orb-QueueMonitor **Detected stale data** 231825ms old, above threshold of 77000ms.

The Data Quality documentation has a suggestion on how to monitor for stale data.

Related articles Copied

• Netprobe disconnects from the Gateway from time to time
• How to fine tune the performance and resource consumption for FKM plugin?
• Managing Load in Geneos