Dynatrace SaaS and Managed monitors
Dynatrace monitors enable the monitoring of resources, processes, and services in an application environment. These monitors give the Controller access to data measured by Dynatrace SaaS, a cloud-based APM tool, and Dynatrace Managed, the on-premises model.
Prepare for Dynatrace monitoring
The Dynatrace SaaS and Dynatrace Managed monitors connect directly to the Dynatrace environment and collect data without requiring a performance test.
If you are using Dynatrace Managed, install it as described in the Dynatrace Managed documentation. The Dynatrace Managed monitor is supported on a variety of Linux platforms. For details, see Managed System Requirements.
To set up Dynatrace monitoring, the following is required:
An active Dynatrace SaaS account.
Dynatrace environment ID. The monitoring environment is where all Dynatrace performance analyses take place. The environment ID is designated by a segment (
<your_environment_ID>.live.dynatrace.com) of the Dynatrace environment URL for Dynatrace SaaS, and
<your_domain>/e/<your-environment-id>for Dynatrace Managed.
Dynatrace API token. The API token grants access to the Dynatrace API, which the Controller uses to query your Dynatrace SaaS environment. Once you have created a token for your environment, it remains the same for every use, unless you change or delete it.
Tip: Save the environment ID and the API token codes so that you can easily copy them when needed.
In your Dynatrace account, go to Settings > Integration > Dynatrace API.
Click Generate token.
Enter a meaningful token name.
In the list of token options, enable Access problems and event feed, metrics, and topology under API v1, and Read metrics under API v2.
This option enables the Controller to request and receive data from Dynatrace.
Scroll down, and click Generate.
Set up the Dynatrace SaaS or Dynatrace Managed monitor
This task describes how to set up the Dynatrace SaaS or Dynatrace Managed monitor.
Note: When the Controller queries Dynatrace for available hosts (Get Hosts), only hosts that have been active in the last hour are taken into account. Therefore, make sure the clock on the LoadRunner Enterprise machine is set to the correct time.
Select a resources folder
Select a resources folder for the monitor profile in the resources tree, or create a new folder as follows:
From the LoadRunner Enterprise navigation toolbar, click and select Monitors (under Assets).
Click New Folder and enter a name for the monitor resources folder.
Create a monitor profile
Click New Monitor Profile, and make sure Monitor Profile is selected.
Enter a name and optional description for the monitor profile, and click Save. An empty monitor profile is added to the selected resources folder.
Select the monitor profile you just added and click Add Monitor.
Select the select Dynatrace SaaS or Dynatrace Managed monitor type.
Click Next and enter the server details:
Your Dynatrace environment ID, in the format:
For Dynatrace SaaS:
For Dynatrace Managed:
For more details on the environment ID, refer to the Dynatrace documentation.
The token string generated by your Dynatrace user account. See create an API token for your Dynatrace environment above.
Select the host that will collect data.
Note: If using more than one host, you need to add each one separately by repeating steps 3c-d.
Click Get Counters to display a list of available metrics and counters per metric from the selected Dynatrace SaaS/Managed host.
Select the measurements that you want to monitor, and then click to add the counters to the Selected Counters table.
Note: The Dynatrace SaaS/Managed monitor has a recommended limit of 50 metrics. See Known issue.
For detailed information on the performance measurements that Dynatrace SaaS/Managed can monitor, see the Dynatrace documentation.
Click Save. The monitor details are displayed in the Monitors tab for the selected monitor profile.
Associate the monitor with your test
For details, see Step 4: Associate monitors with your test.
The Dynatrace API has an access limit of 50 requests per minute, meaning you should not select more than 50 measurements in total, for all hosts combined.
The Selected Measurements box prevents you from selecting more than 50 metrics for one host, but does not prevent you from exceeding this number when setting up metrics for multiple hosts (such as 40 metrics on one host and 20 metrics on another). If the limit is exceeded, it is likely that some of the data will not be received.