Dynatrace Hub - Traceroute latest releases

Traceroute 4.0.1

Mon, 18 May 2026 11:12:45 +0000

This version requires a minimum Dynatrace version of 1.338.0 and a minimum EEC version of 1.318.0.
This version includes a potentially breaking change for Dynatrace on Grail.
- With the inclusion of OpenPipeline processing rules, any metrics ingested from the extension will be processed by a dedicated OpenPipeline pipeline instead of the default pipeline.
- This means that any created custom dynamic rules will no longer be used on metrics ingested from the extension. If you want to keep enforcing them, please create pipeline groups.
- Additionally, some field names are handled differently in OpenPipeline, e.g. capitalization. Please double-check any custom dashboards and alerts you have created for this extension.
- You must opt-in to OpenPipeline configuration via Settings API – see the documentation.

Smartscape on Grail. This extension will populate new Smartscape edges via OpenPipeline extraction.
Enrichment of Traceroute metrics with Smartscape on Grail information via DQL: you can optionally pass a Dynatrace API Platform Token to match your existing network devices to the metrics ingested by this extension.

Fri, 13 Mar 2026 02:03:28 +0000

Thu, 18 Dec 2025 20:48:55 +0000

🐛 Bugs fixed in this version:

Fixed a bug in which the platform dashboard would prompt for changes to be saved/discarded

Fri, 05 Dec 2025 10:49:22 +0000

Note this may be a Breaking change to custom dashboards.

Fixes and Improvements:

Removed volatile dimension trace.start. Trace start is now determined from the metric ingest timestamp instead. You can see examples of how to do this in the 'Traceroute Connectivity' Dashboard.
Remove redundant dimensions next.name and next.address. Network topology can be derived solely from the previous.name and previous.address dimensions. This doubly linked list approach was not needed.

Deprecations:

Tue, 04 Nov 2025 13:31:55 +0000

🚀 Improved in this version:

Tue, 19 Aug 2025 13:13:17 +0000

Mon, 09 Jun 2025 12:28:10 +0000

Bug Fix: Resolves an error when checking if the last device was the expected destination, when the device list was empty
Updated both the classic and document dashboards.

Tue, 27 May 2025 12:52:50 +0000

Tue, 20 May 2025 07:00:10 +0000

Now correctly processes traces where probes for the same hop go to different devices (e.g. load balanced)

Now uses Dynatrace standard dimension naming for device Ip address and hostname information. e.g., device.address and device.name instead of device.hostname and device.ip.
- The existing topology type for a Traceroute Device is unchanged.

Thu, 13 Mar 2025 00:15:49 +0000

Run traceroute command. e.g.,
- Linux: traceroute -w 1 --max-hops=10 google.com
- Windows: tracert -w 1000 -h 10 google.com
Collect RTT and connection status metrics
Dashboards, topology and Unified analysis screens