# Dynatrace integrations: problems

> Dynatrace is an observability platform that monitors applications, infrastructure, and logs, detects problems automatically, and reports on performance…

**Canonical page:** https://tray.ai/connectors/dynatrace-integrations/
**Categories:** IT
**Connects through:** HTTP Connector

## Overview

Dynatrace is an observability platform that monitors applications, infrastructure, and logs, detects problems automatically, and reports on performance and reliability. Tray.ai connects to Dynatrace through the HTTP Connector, so your workflows can call the Dynatrace API alongside the rest of your stack.

## Use cases

### Problems

Read problems in Dynatrace from any Tray.ai workflow. The Dynatrace API covers calls such as list problems and get problem details.

- List problems
- Get problem details
- Close a problem

### Problem comments

Read, create, update, and delete problem comments in Dynatrace from any Tray.ai workflow. The Dynatrace API covers calls such as list comments and post a comment.

- List comments
- Post a comment
- Edit a comment

### Events

Read events in Dynatrace from any Tray.ai workflow. The Dynatrace API covers calls such as list events and list event types.

- List events
- List event types
- Ingest an event

### Metrics

Read metrics in Dynatrace from any Tray.ai workflow. The Dynatrace API covers calls such as list metrics and get metric data points.

- List metrics
- Get metric data points
- Ingest metric data points

## Challenges Tray.ai solves

### Keeping Dynatrace credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Dynatrace credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Dynatrace API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Dynatrace API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Dynatrace?

Yes. Tray.ai connects to Dynatrace through the HTTP Connector, which calls the Dynatrace API directly. Any call the Dynatrace API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Dynatrace?

The Dynatrace API uses an API key in a request header, a bearer token, and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Dynatrace connector?

Dynatrace runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Dynatrace connector from the Dynatrace API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/