Synthetic Classic has reached end of support and is no longer available. Existing Synthetic Classic customers have been upgraded to the all-in-one Dynatrace software intelligence platform.

Diagnosing Private Last Mile runtime issues

Use the following procedure to diagnose runtime issues.

Test the connectivity to the Dynatrace infrastructure.

From the Private Last Mile machine, try to open a browser connection to the following URLs.

If any of the above URLs fails to connect, review the requirements for running the peer.

Determine whether the Private Last Mile machine has checked in recently.
You can find this information in the Private Last Mile Network Machine Profile page.

Verify that the peer is running.
In the Processes tab of the Windows Task Manager, look for GomezPEERSvc.exe and java.exe. If either of these processes is missing, review the procedures for installing and running the peer.

If the problem persists, send the debug log files to Customer Support.

In the Preferences dialog box, select Kernel Logging and TRACE.
If the private peer client has been unable to start, enable the debug log as described below.

Reproduce the problem so that it appears in the debug logs.

Send the log files and a description of the problem to Customer Support.
The log files ppeer-debug.log* and ppeer-debug-ui.log* are located in <installationdirectory>\logs, where the default for <installationdirectory> is C:\Program Files (x86)\Dynatrace\PrivateLastMile.

If the PLM peer client has been unable to initially start, complete these steps below to enable the debug log and set debugging to TRACE:

  1. Shut down the private peer client service in the private peer client UI through Options in the tool bar, and confirm that it is stopped through the Windows Control Panel.
  2. Open the loggerprops.xml file in the peer directory %\Dynatrace\PrivateLastMile (the default is C:\Program Files (x86)\Dynatrace\PrivateLastMile) into a text editor.
  3. Change the attribute value to TRACE for the element <priority> under the parent element <root>.
    The default value is <priority value="INFO"/>; after editing, the element is <priority value="TRACE"/>.
  4. Save the loggerprops.xml file (using Save, not Save As).
  5. Delete the ppeer-debug.* files in the %\Dynatrace\PrivateLastMile\logs directory.