• Dynatrace Portal

When a Trace Route is run from the Dynatrace Portal, it can produce several messages that look like errors. These messages include:

  • Operation failed
  • A timeout occurred
  • Name lookup failed

A Trace Route tracks the path of packets as they travel across an IP network, typically from a local system to a remote server. Every step of a trace route queries the current device for its next travel destination based on its cache or IP routing table. Once a response is received, the trace route measures the packet travel time in milliseconds, and determines the name of the next destination device.

Typically, trace routes are used for network troubleshooting. By investigating the routers that your data travels through in order to get to their destination, you may be able to determine the cause of delays or bottlenecks.

The Trace Route test records the path sequence, or hops, taken by data. When the test is complete, it will display:

  • The IP address.

  • Host name.

  • The sequence's Response Time.

  • A result message.

Trace routes are run from the Instant Test tab of the Diagnostics page in the Dynatrace Portal. You can run a trace route for any Backbone Single URL or Transaction test, a Last Mile test, or a Mobile test.

Trace Route messages do not indicate problems with the Trace Route feature. They detail issues found during the trace route:

  • Operation failed – The name lookup for the remote system succeeded; however, the system failed to respond.

  • A timeout occurredThe connection with the remote system succeeded; however, a timeout occurred before the communication could be completed.

  • Name lookup failedThe IP address for the domain name could not be found.

  • Echo ReplyThe data successfully reached its destination.

The Trace Route can recover and proceed from each of these situations. Most Trace Route programs hide these messages. The Dynatrace Portal, however, displays them, because knowing exactly what happened during the trace route can be useful in locating and identifying any network issues.





  • No labels