Dynatrace integration

Connect DXDT to Dynatrace via the Environment API v2 for read-only observability: Davis-detected problems with impact and root cause, monitored entities (hosts, services, applications, process groups), and available metric keys. This supports incident diagnosis. DXDT reads only — it never acknowledges, closes, or configures anything in Dynatrace.

Setup time	~7 minutes
Difficulty	Easy

Access required: Your Dynatrace environment URL and an Access Token with read-only scopes (problems, entities, metrics).

Prerequisites

• Permission to create Access Tokens in your Dynatrace environment (Settings → Access Tokens).
• Your Dynatrace environment URL: SaaS https://<env-id>.live.dynatrace.com, or a Managed cluster URL like https://<cluster>/e/<env-id>.

Setup

1. Create a read-only Access Token

In Dynatrace, go to Settings → Access Tokens (or Access Tokens in the newer navigation) and create a new token. Grant only the read scopes needed by DXDT, then copy the token — it is shown once. This becomes api_token.

• Add scope metrics.read (Read metrics).
• Add scope entities.read (Read entities).
• Add scope problems.read (Read problems).
• Do not add any write, settings, or admin scopes.

2. Identify your environment URL

For Dynatrace SaaS, use https://<env-id>.live.dynatrace.com. For Dynatrace Managed, use the cluster URL in the form https://<cluster-host>/e/<env-id>. This becomes env_url. Do not append an API path — DXDT adds /api/v2 itself.

3. Enter the configuration in DXDT

In the DXDT marketplace, open the Dynatrace plugin. Enter env_url and paste the api_token. Save to install.

Configuration fields

Field	Where to find it
Environment URL (env_url)	Dynatrace environment URL — SaaS https://<env-id>.live.dynatrace.com or Managed https://<cluster>/e/<env-id>. Required.
API Token (api_token)	Dynatrace Access Token with read scopes metrics.read, entities.read, problems.read. Required. Sent as Authorization: Api-Token.

Verify the connection

On save, DXDT calls ping, which validates the token and connectivity. Success confirms the URL and scopes are correct; you can then ask DXDT to list problems or list entities HOST to confirm read access.

Security

DXDT uses only read scopes against the Dynatrace Environment API v2 — no acknowledging, closing, or configuration. Grant the Access Token nothing beyond metrics.read, entities.read, and problems.read, and rotate it periodically.

Troubleshooting

401 Unauthorized on ping

The api_token is invalid, revoked, or belongs to a different environment than env_url. Recreate the token in the correct environment and confirm env_url matches that environment's ID.

403 on list problems/entities/metrics

The token is missing the required read scope for that resource. Edit the token and add the specific missing scope (problems.read, entities.read, or metrics.read).

Connection error on Managed deployments

env_url omits the /e/<env-id> path required for Dynatrace Managed clusters. Use the full Managed form https://<cluster>/e/<env-id> as env_url.

---

Vendor documentation: https://docs.dynatrace.com/docs/dynatrace-api/basics/dynatrace-api-authentication