Dynatrace SaaS monitor

Use this monitor to integrate with the Dynatrace SaaS platform, enabling the Controller to access data measured by Dynatrace SaaS—a cloud-based APM tool. Dynatrace SaaS enables monitoring of resources, processes, and services in an application environment.

In this topic:

Set up the Dynatrace SaaS monitoring environment

The Dynatrace SaaS monitor connects directly to the Dynatrace environment and collects data without requiring a performance test.

To set up Dynatrace SaaS monitor, 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 (<unique-string>.live.dynatrace.com) of the Dynatrace environment URL.
  • 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 permanent.

Keep a note of the ID and the API token codes so that you can easily copy them when needed.

To create an API token for your Dynatrace environment:

  1. In your Dynatrace account, go to Settings > Integration > Dynatrace API.

  2. Click Generate token.

  3. Enter a meaningful token name.

  4. In the list of token options, enable Access problems and event feed, metrics, and topology.

    This option enables the Controller to request and receive data from Dynatrace.

  5. Scroll down, and click Generate.

Back to top

Configure the Dynatrace SaaS monitor

This task describes how to configure the Dynatrace SaaS 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.

To configure and monitor data from Dynatrace SaaS:

  1. Prerequisites

    • You must set up a web proxy to collect data from the server as described in Use a proxy server.

    • LoadRunner Enterprise 2020 SP2 only: Make sure that LoadRunner Enterprise is able to successfully ping the machine where the Dynatrace Agent is installed. If there is a firewall blocking the ICMP (ping) request, you won’t be able to get the metrics.

    • For the supported server versions, see the Integrations section of the System Requirements guide.

  2. Configure the Dynatrace SaaS monitor from the monitor profile

    1. From the LoadRunner Enterprise navigation toolbar, click and select Monitors (under Assets).

    2. In the test resource tree, select an existing monitor profile, or click New Monitor Profile and create a new monitor profile.

    3. In the Monitor Profile page, click Add Monitor and select Dynatrace SaaS.

    4. In the Dynatrace SaaS page, enter the server login details:

      UI Elements

      Description
      Server

      Your Dynatrace environment ID, in the format <unique-string>.live.dynatrace.com.
      Token

      The token string generated by your Dynatrace user account. See create an API token for your Dynatrace environment above.

  3. Click Get Hosts and select the host that will collect data.

    Note: If the host name is a friendly name that is not in the domain format (such as "qa_app"), then you must add the IP address to the C:\Windows\System32\drivers\etc\hosts file on the LoadRunner Enterprise server in the format <host_ip> <host_name>.

    For example: 10.111.13.153 qa_app

  4. If using more than one host, you need to add each one separately by repeating steps 2c-3.

  5. Click Get Counters to display a list of available metrics and counters per metric from the selected Dynatrace SaaS host, and select the relevant measurements that you want to monitor.

    Note: The Dynatrace SaaS monitor has a recommended limit of 50 metrics. See Known issue.

    For detailed information on the performance measurements that Dynatrace SaaS can monitor, see the Dynatrace documentation.

Back to top

Known issue

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.

Back to top

See also: