Netprobe Memory Debugging

Overview Copied

The Netprobe has memory protection variables that prevent it from consuming too much memory.

For example, the following Netprobe log entry is an indication that memory protection features have been triggered:

The said features are triggered when the memory threshold is about to be breached. The threshold can be modified by changing the memory protection settings. For more information, see Netprobe Memory Protection Settings.

This topic walks you through the setup of memory debugging in the Netprobe.

Note

The memory discussed in this guide is the Netprobe virtual memory.

Caution

It is not recommended to interpret the Netprobe memory logs in isolation. This option is presented to aid in troubleshooting. For further assistance, contact ITRS Support .

Set up memory debugging Copied

1. In the Gateway Setup Editor, select the probe that you want to debug.

2. In that probe, select the Debug tab.

3. Under the Debug field, click Add new to add the following two modules:

   • SAMPLING
   • SAMPLINGMEM

4. For each module, click Setting. The Setting window appears.

5. In the Setting window, add * to the Setting field and click Close.

6. Under the General debug field, click Add new to add the MEM_UTIL module.

7. Click Save current document to apply your changes.

   Success

   The SAMPLING and SAMPLINGMEM modules begin to appear on the Netprobe log file. The MEM_UTIL module start writing to the log every ten minutes.

Indication of success Copied

To know if memory debugging is running as set, check the Netprobe logs for the following:

SAMPLING and SAMPLINGMEM logs come as a set of IN and OUT logs.

The MEM_UTIL logs write to the log every ten minutes:

Further reading Copied

For more information on Netprobe memory protection, see Netprobe Memory Protection Settings.