Appearance
Dynatrace
Monitor entities, query metrics, and manage problems and SLOs with the Dynatrace API.
| Detail | Value |
|---|---|
| Category | Monitoring |
| Base URL | https://{environment-id}.live.dynatrace.com/api/v2 |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | dynatrace |
Using Dynatrace in a workflow
- Go to Connections and click New Connection.
- Pick Dynatrace from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /entities | List monitored entities |
GET /entities/{entityId} | Get entity details |
GET /metrics/query | Query metric data |
GET /metrics | List available metrics |
GET /problems | List detected problems |
GET /problems/{problemId} | Get problem details |
GET /slo | List SLOs |
GET /events | List events |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /entities
List monitored entities
| Detail | Value |
|---|---|
| Operation ID | monitoring.listEntities |
| Method | GET |
| Path | /entities |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Dynatrace connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.listEntities. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Dynatrace API reference.
GET /entities/{entityId}
Get entity details
| Detail | Value |
|---|---|
| Operation ID | monitoring.getEntity |
| Method | GET |
| Path | /entities/{entityId} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Dynatrace connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.getEntity. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Dynatrace API reference.
GET /metrics/query
Query metric data
| Detail | Value |
|---|---|
| Operation ID | monitoring.queryMetrics |
| Method | GET |
| Path | /metrics/query |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Dynatrace connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.queryMetrics. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Dynatrace API reference.
GET /metrics
List available metrics
| Detail | Value |
|---|---|
| Operation ID | monitoring.listMetrics |
| Method | GET |
| Path | /metrics |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Dynatrace connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.listMetrics. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Dynatrace API reference.
GET /problems
List detected problems
| Detail | Value |
|---|---|
| Operation ID | monitoring.listProblems |
| Method | GET |
| Path | /problems |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Dynatrace connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.listProblems. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Dynatrace API reference.
GET /problems/{problemId}
Get problem details
| Detail | Value |
|---|---|
| Operation ID | monitoring.getProblem |
| Method | GET |
| Path | /problems/{problemId} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Dynatrace connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.getProblem. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Dynatrace API reference.
GET /slo
List SLOs
| Detail | Value |
|---|---|
| Operation ID | monitoring.listSLOs |
| Method | GET |
| Path | /slo |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Dynatrace connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.listSLOs. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Dynatrace API reference.
GET /events
List events
| Detail | Value |
|---|---|
| Operation ID | monitoring.listEvents |
| Method | GET |
| Path | /events |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Dynatrace connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.listEvents. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Dynatrace API reference.