---
title: "Netprobe Memory Debugging"
description: ""
url: "https://docs.itrsgroup.com/docs/geneos/7.11.0/collection/troubleshooting/netprobe-memory-debugging/index.html"
---
## Overview

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:

```
ERROR: NetProbe Restart Message: IMPORTANT - Contact your support provider; if supported directly by ITRS then mailto:support@itrsgroup.com (0) otherwise your usual support contact
```

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](/collection/troubleshooting/../netprobe/configuration/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](mailto:support@itrsgroup.com)
. 


## Set up memory debugging

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** ![](https://docscdn.itrsgroup.com/geneos/images/Icons/save16x16.png "icon") to apply your changes.
![GSE probe memory debug modules](https://docscdn.itrsgroup.com/geneos/images/netprobe/probe-debug-memory-protection.png)

**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

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

```
<Thu Nov 07 00:25:15> DEBUG: SAMPLING:* IN : MQ-QINFO[M Queue Info]
<Thu Nov 07 00:25:15> DEBUG: SAMPLINGMEM:* IN : workingSet = 12066816 bytes, pagefileUse =16617472 bytes
<Thu Nov 07 00:25:15> DEBUG: SAMPLINGMEM:* OUT : workingSet = 12189696 bytes, pagefileUse = 16650240 bytes, memoryDifference = 122880 bytes, memoryDifferenceTotal =1200128 bytes
<Thu Nov 07 00:25:15> DEBUG: SAMPLING:* OUT : MQ-QINFO[MQ Queue Info] [0.000000 sec]
```

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

The `MEM_UTIL` logs write to the log every ten minutes:

```
<Wed Jul 24 07:29:19> INFO: MEM_UTIL INFO: Netprobe mem utilisation 1428196 KB from 510940 KB
<Wed Jul 24 07:39:22> INFO: MEM_UTIL INFO: Netprobe mem utilisation 1446628 KB from 510940 KB
<Wed Jul 24 07:49:28> INFO: MEM_UTIL INFO: Netprobe mem utilisation 1465044 KB from 510940 KB
<Wed Jul 24 07:59:33> INFO: MEM_UTIL INFO: Netprobe mem utilisation 1496724 KB from 510940 KB
```

## Further reading

For more information on Netprobe memory protection, see [Netprobe Memory Protection Settings](https://docs.itrsgroup.com/docs/geneos/7.11.0/collection/netprobe/configuration/netprobe-memory-protection-settings/index.html).