Private Synthetic Location not available for ICMP (NAM) monitors in Dynatrace

HannahM · ‎13 May 2026

Summary

This article focuses on Dynatrace Synthetic Monitoring, specifically Network Availability Monitors (NAM) using ICMP, and explains why a new private Synthetic location may not be selectable when creating ICMP monitors. It helps users understand the platform prerequisites and system-level dependencies that determine whether ICMP monitoring is available from a private location.

Summary
Problem
Troubleshooting steps
Resolution
After resolving the cause of the failure
What’s next
Related reading

Problem

After deploying Synthetic-enabled ActiveGates and assigning them to a new private Synthetic location, the location appears as “Not supported” when attempting to create an ICMP (Network Availability) monitor.

In the Dynatrace UI:

Synthetic app> Private locations. The private location shows a Compatibility health alert.
Network Availability (ICMP) is missing from the available monitor types in Classic Settings> Web and Mobile monitoring> Private Synthetic locations> Edit location.
The private location marked as Not supported, with an message indicating that the Location is not configured to execute this type of monitor.

ActiveGate diagnostic logs, vuc-status.log, show that ICMP is marked as unavailable, even though other Synthetic capabilities (Browser, HTTP, TCP, DNS) are operational.

2026-05-12T14:10:22,211Z [DiagnosticResultsHolder]
	multi-protocol = `DiagnosticResultsChangedEvent[moduleName=MULTIPROTOCOL, diagnosticCasesResult=DiagnosticCasesResult[isOperational=true, cases={MULTIPROTOCOL_TCP=DiagnosticCaseDetail[isAvailable=true], MULTIPROTOCOL_DNS=DiagnosticCaseDetail[isAvailable=true], MULTIPROTOCOL_ICMP=DiagnosticCaseDetail[isAvailable=false]}]]`

Troubleshooting steps

Review ActiveGate diagnostic results in the vuc-status.log to confirm whether ICMP is reported as available or not.
MULTIPROTOCOL_ICMP=DiagnosticCaseDetail[isAvailable=false]

2026-05-12T14:10:22,211Z [DiagnosticResultsHolder]
	multi-protocol = `DiagnosticResultsChangedEvent[moduleName=MULTIPROTOCOL, diagnosticCasesResult=DiagnosticCasesResult[isOperational=true, cases={MULTIPROTOCOL_TCP=DiagnosticCaseDetail[isAvailable=true], MULTIPROTOCOL_DNS=DiagnosticCaseDetail[isAvailable=true], MULTIPROTOCOL_ICMP=DiagnosticCaseDetail[isAvailable=false]}]]`

For information on finding the log see Useful Synthetic ActiveGate logs

Verify whether the ping command is present and executable on the ActiveGate host operating system.
- For Windows ActiveGates, also check using Test-NetConnection
Confirm that the operating system and environment allow ICMP execution at the system level.
Confirm that ping, or Test-NetConnection on Windows, to localhost is allowed, this the test used by the ActiveGate to confirm that ping is allowed.
```
sudo -H -u dtuserag bash -c 'ping -c 1 -s 32 -W 1 -i 0.2 127.0.0.1'
```

These checks help determine whether the limitation is related to the Dynatrace configuration or to host-level ICMP support.

Resolution

ICMP availability in a private Synthetic location depends on the underlying host’s ability to execute ICMP operations.

Note: ICMP checks on Linux-based Private Synthetic Locations rely on the ping process, while Windows locations use a native API-based implementation for improved efficiency. This may lead to differences in resource usage and behavior across platforms.

If ICMP is not enabled or available on the ActiveGate host, including to localhost:

Dynatrace will mark ICMP as unavailable in diagnostic results.
The private location will not support ICMP (NAM) monitors, even though other Synthetic monitor types are available.

Ensuring that the host operating system supports ICMP is a prerequisite for enabling ICMP-based Network Availability Monitoring from private Synthetic locations.

For containerized synthetic-enabled ActiveGates, additional permissions are required for running ICMP tests. The details can be found here.

After resolving the cause of the failure

After resolving the cause of the failure, restart the Synthetic module:

Linux:
systemctl restart vuc.service
Windows:
Restart the Dynatrace Synthetic service.

What’s next

If none of the previous steps resolved the issue, open a chat and provide the Support Archive from the ActiveGate with the troubleshooting steps you have already completed.