Traceroute extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Run traceroute commands and collect step performance metrics.
Get started
Overview
Pinpoint network latency and routing issues by visualizing traceroute paths across your hosts.
Simply activate the extension in your environment using the in-product Hub, provide the necessary device configuration and you’re all set up.
For Linux hosts, you will also need to have installed the traceroute command.
This extensions runs a traceroute (or tracert on Windows) command from an ActiveGate or OneAgent to a configured destination and collects all of the RTT performance metrics for each step.
It also collects a metric on whether the connection to the remote destination was successful (1) or failed (0).
Each metric contains dimensions for the device IP/hostname of each hop.
Use cases
- Collect connection information and performance for layer 3 network devices.
- Diagnose network outages.
Compatibility information
- Windows
- Linux (Requires
tracerouteto be installed)
Details
This extension calls the traceroute command on Linux hosts, or the tracert command on Windows hosts.
- Linux:
traceroute -w 1 --max-hops=10 google.com - Windows:
tracert -w 1000 -h 10 google.com
The RTT metrics for each device hop are then processed and sent to Dynatrace.
The extension package contains:
- Extension Library,
- Overview dashboard
- Custom Topology types extracted from metric dimensions
- Traceroute Device
- Relationships to correlate a
dynatrace:traceroute_deviceto anetwork:device
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
default
| Metric name | Metric key | Description |
|---|---|---|
| Traceroute RTT | traceroute.rtt | Traceroute Round Trip time |
| Traceroute Connected Successfully | traceroute.connection | Could the traceroute reach the destination? 1 = Yes, 0 = No |
