I just started to use Private Last Mile and have PLM peers installed. When I created a Private Last Mile test, on the test configuration page, I saw no peers listed there to select.

Anything else needs to be done?


Dynatrace Synthetic Classic: Private Last Mile (PLM)


One thing to clarify is that PLM tests are not directly scheduled to run from the PLM peers you have installed. PLM tests are scheduled onto the PLM Peer Populations. Then use the criteria defined in the Peer Population to look for peers. After that the tests are assigned to those peers that are found with the same criteria.

In other words, Peer Population is a group of peers. That you define criteria to search for peers. So that you can easily group multiple peers together when you need it. (See here for details about how does PLM tests scheduling work.)

Thus under the test configuration page, what listed there is the list of the peer populations you have created but not the peers installed.

PLM Peer Population is created on the Adding peer population page. Click here to go to the related doc page for details. There can be just one peer or multiple peers under one peer population. 

To summarize, please set up peer populations before you set up PLM tests, 

Best Practices:

On the Configure New Private Peer Population page, there are 11 fields/criteria can be configured:

  • 2 fixed fields: that need to be set up for ALL PLM peer populations;
  • 9 custom fields: using one field to configure one PLM peer population is fair enough. We recommend* either using field "Choose Machine" or "Choose User Defined Fields".
    *: Do not recommend using fields like the region/country. As by default we determine the location of the peer by its IP. It often happens that the peer machine is using your company proxy or VPN. In that case, the location determined by IP is different as the physical location. If you set the region/country of the peer as its physical location, we cannot find the peer.

How to set the 2 fixed fields:

  • The Peer (Population) Name

--Name it with something that makes sense to you and your team. With which you can easily recognize what peers are included under the Peer Population.

Not recommended to name it with the same name as your Private Last Mile Network. Two different things with the same name will be confusing.

It is commonly used to include the Region/Country where the peers are located and/or your team or project name in the name of a Peer Population Name.

For example: SyntheticUKPLMPeers or DynatraceUSPLMPeers

  • The Private Last Mile Network

--It is the name of your Private Last Mile Network. Which was provided to you when Private Last Mile was enabled for your account, either by your Account Manager, or directly sent by the Licensing team.

When you configure your PLM peers, on the Preferences page, the "Account Name" there is actually  "(Network) Account Name" which means the same thing here: name of your Private Last Mile Network.

How to set the custom fields:

If you want to create a peer population which includes all your peers, setting up the two fixed fields is enough. No need to select custom fields. Since all your peers are linked with a PLM Network, with PLM Network(s) selected, that is enough criteria for our system to find all your peers.

To create a PLM peer population which includes some of your peers, select either one of the custom fields below is enough.

    •  Choose Machine
      --Find and select the name of the peer machines you desire to use. This will tell our system which machines to select directly.
      The advantage of using this setting is you can see directly which peers are included.
      The disadvantage is that you need to update the population setting after your peers are changed. Like when a new peer is installed. This might sound trivial but is easily overlooked and this new peer will not be able to take new jobs, since it is not included under any peer population.

    • Choose User Defined Fields
      --User Defined Fields are configured on the peer UI too. Under Options > Preferences page. We recommend listing the City name as User Defined Field 1 as our Charting will pull User Defined Field info as city.
      The advantage of using User Defined Fields is it is very agile. Say you have two peers in UK and want to put them under the same peer population. Simply list UK as the value of User Defined Field 2 or 3 for both of your peers. Then configure the peer population using User Defined Field 2 or 3. And when you install a new UK peer and need to put it under the same peer population, you do not need to update the population setting. Simply list UK as the same User Defined Field will do.