Integration

Dynatrace integration

Software intelligence platform API for application performance monitoring, infrastructure monitoring, and AI-powered operations. Access metrics, traces, logs, and real user data. Features include automatic root cause analysis, anomaly detection, and full-stack observability. Used by enterprises for digital experience monitoring and cloud operations.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Dynatrace.Built from the 17 Dynatrace tools below, on the connection you add once.

Common Dynatrace use cases

  • deployment tracking
  • alerting
  • dashboards
  • entity details
  • custom analysis
  • troubleshooting
  • entity discovery
  • metric discovery
  • custom monitoring
  • event investigation

What you can do with Dynatrace

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Problem, 4 operations

  • add_problem_commentAdd problem commentPOSTPosts a comment on a problem for collaboration. Requires problems.write scope.
  • close_problemClose problemPOSTCloses a problem with a comment. Requires problems.write scope.
  • get_problemGet problemGETGets detailed problem information. Returns root cause analysis, affected entities, events timeline, and impact assessment.
  • list_problemsList problemsGETLists detected problems with AI analysis. Filter by status, severity, entity. Returns root cause and impact assessment.

Event, 3 operations

  • get_eventGet eventGETGets details of a specific event including type, properties, and affected entities.
  • ingest_eventIngest eventPOSTIngests custom events to Dynatrace. Create deployments, annotations, alerts, or info events on entities.
  • list_eventsList eventsGETLists events detected by Dynatrace. Returns deployment events, configuration changes, anomalies, and custom events.

Metric, 3 operations

  • ingest_metricsIngest metricsPOSTIngests custom metric data points. Uses Dynatrace line protocol. Metrics auto-created on first ingest.
  • list_metricsList metricsGETLists all available metrics in the environment. Returns metric keys, display names, units, and dimensions.
  • query_metricsQuery metricsGETQueries metric time series data. Use metric selectors to specify what to retrieve. Filter by entity, time range, and resolution.

Monitored entity, 2 operations

  • get_entityGet entityGETGets entity details including properties, tags, and topology relationships. Full context for any monitored component.
  • list_entitiesList entitiesGETLists monitored entities with flexible filtering. Query hosts, services, processes, applications by type, tags, or properties.

Dql, 1 operation

  • run_dql_queryRun dql queryPOSTExecutes a DQL query for flexible data analysis. Query metrics, logs, events, and entities with SQL-like syntax.

Entity type, 1 operation

  • list_entity_typesList entity typesGETLists all entity types available in the environment. Returns type names, properties, and relationships.

Log, 1 operation

  • search_logsSearch logsGETSearches log data with query expressions. DEPRECATED - use DQL query with 'fetch logs' instead.

Synthetic execution, 1 operation

  • get_synthetic_http_monitor_executionGet synthetic http monitor executionGETGets the most recent HTTP monitor execution result. Returns pass/fail, response times, and error details.

Synthetic monitor, 1 operation

  • list_synthetic_monitorsList synthetic monitorsGETLists synthetic monitoring tests. Returns browser and HTTP monitors with configuration and status.

Use Dynatrace from Claude Code, Cursor or Codex

Connect Dynatrace in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Dynatrace operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Dynatrace

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Dynatrace once

    Add your Dynatrace connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Dynatrace integration FAQ

What can you do with the Dynatrace integration?

LiveContext exposes 17 operations on Dynatrace, covering problem, event, metric and monitored entity. Common uses include deployment tracking, alerting and dashboards.

Popular integrations

Browse the whole catalog