The Current Instant Tests window displays the list of Backbone, Last Mile, Private Last Mile, and Mobile Instant Tests.
This window appears when you select View current Instant Test results at the bottom of the Diagnostics page.
All tests expire two hours after they are launched.
The window refreshes itself every minute so that up-to-date information always appears.
The columns that appear on this page depend on whether you are viewing Backbone, Last Mile, or Mobile Instant Tests:
Test Name – Test or URL that was run.
Peer Pop/Machine – Machine name or Peer Population from which the test was executed. (Last Mile or Mobile only)
Node – Node on which the test was run. (Backbone only)
Launched At – Date and time the test was launched.
Expires At – Date and time the test will expire (2 hours after launch time).
Last Machine Checkin – Last date and time the selected machine checked in. (Last Mile or Mobile only)
Type – Type of Instant Test selected.
Agent Type – Type of agent that ran the Instant Test.
IP Preference – Whether the test was run on IPv4 or IPv6.
IPv6 is supported only for Private Last Mile tests using the IE Agent, Firefox Agent, or Chrome Agent.
Response Time – Response time (in seconds) of a successfully completed test.
Status – One of the following: Waiting for machine, In Progress, Complete, or Failed.
The Failed status means that for some reason, the test did not run.
You can sort on any of the column headings; the Launched At column is the default with the oldest test on top.
After a test completes, the following icons appear in the Status column:
View the results of this test. If the test failed to execute, this icon does not appear.
View a screen capture for this test (Mobile tests only).
Rerun this Instant. Test. For an NS Lookup test, it uses the same name server.
Delete this test.
The HTTP test result shows a waterfall chart that displays the end-to-end page download time as well as all object details that make up the page download time.
The time for each object is broken down by component:
- Page Download Time
- DNS Time
- Connect Time
- SSL Time
- First Byte Time
- Content Time metrics
Any errors on a page or object within the text are highlighted in the chart. Hover over a bar in the chart to view the component detail and associated time.
For Last Mile, Private Last Mile, or Mobile tests, click view definition to open a window, which lists the included and excluded criteria for this peer (location). Click the machine number to open a window that displays specific information (such as operating system or IP address) for this machine.
Email this page by clicking located at the top right corner of this page.
Below the waterfall chart is the Object Response Time Data table, which lists the values displayed in the waterfall chart for each of the objects, along with information such as the type of object and return codes. Any errors on a page or object are also highlighted in the data table. If you selected to view request/response header capture information when you created the test, then a link appears for each object (excluding connection types) that you can select to view this information.
The results of a Ping test display in tabular view, showing the sequence, IP Address, Host, Response Time, and Message of the request.
The results of a NS Lookup test displays in tabular view, showing the host, type, and data returned.
The results of a Trace Route test displays in tabular view, showing the sequence, IP Address, Host, Response Time, and Message of the request.
Trace Route results typically list the connection points for one particular set of messages from the client machine to the target server, and report the latency for a network packet to the intermediate servers. Trace Route results in Last Mile average the latency for three test packets for each intermediate server hop.
The geographic information for each server hop is resolved in a similar fashion to the validation for client Last Mile machines. That is, Dynatrace uses the IP address to determine the general geographic location for that server.
Each hostname lookup is performed at the client machine, and is determined to be the first returned host or IP for a particular instance. These lookups are dependent on the client machine’s DNS systems. Typically, this means interactions with a short-lived Windows cache and ISP level DNS servers.
If there is a significant jump in latency at or for a particular hop, it suggests a bottleneck from the Tier 1 provider just prior to the jump to the Tier 1 provider just after the jump. This may indicate peering issues between these providers, or a regional issue with routing within a particular provider. Following up with these providers or researching related issues may be warranted in these cases.
The following is an example of the results for TcpTrace:
The following is an example of the results for Dig:
Sending a current instant tests view
Click the Send icon in the upper right corner of the Current Instant Tests window to email the current window.
The recipient receives the current “view on send time.” This view may not match your view exactly as tests may expire and tests that are “In Progress” in your view may complete before sending the view.