Dynatrace

Dynatrace

This connector works with Dynatrace through the Environment API v2 (<environment>/api/v2) and an access token: problems found by Davis AI, monitored entities and tags, metrics and metric queries, log search, events, security problems (vulnerabilities), SLOs, settings (read only) and the audit log. It can comment on problems, send custom events (e.g. deployments) and tag entities.

Setup (3 minutes)

1. DYNATRACE_ENVIRONMENT_URL: the classic environment address, https://<environment-id>.live.dynatrace.com for SaaS or https://<your-domain>/e/<environment-id> for Managed, without /api and without a trailing slash. The new platform address (<environment-id>.apps.dynatrace.com) does not take this kind of token; use the live address of the same environment.
2. In Dynatrace open Access tokens (Manage, Access tokens, Generate new token) and tick the scopes the tools need: problems.read, entities.read, metrics.read, logs.read, events.read, securityProblems.read, slo.read, settings.read, auditLogs.read; for writes problems.write (comments, closing), events.ingest and entities.write (tags). A personal access token (dt0c01) works the same way.
3. Paste the token into DYNATRACE_API_TOKEN and run dynatrace_list_problems to check it.

Workflow

• What is broken: dynatrace_list_problems with problem_selector: status("OPEN"), then dynatrace_get_problem with fields: evidenceDetails,impactAnalysis for root cause and impact, dynatrace_list_problem_comments and dynatrace_add_problem_comment. dynatrace_close_problem closes a problem by hand.
• Topology: dynatrace_list_entity_types, dynatrace_get_entity_type, dynatrace_list_entities (e.g. type("SERVICE"),entityName.contains("checkout")), dynatrace_get_entity for properties and relationships, dynatrace_list_tags and dynatrace_add_tags.
• Numbers: dynatrace_list_metrics (search with text), dynatrace_get_metric, then dynatrace_query_metrics with a metric selector.
• Logs: dynatrace_aggregate_logs to see where errors cluster, then dynatrace_search_logs for the records.
• Changes and events: dynatrace_list_events (e.g. eventType("CUSTOM_DEPLOYMENT")), dynatrace_get_event, dynatrace_list_event_types; record a deployment or change with dynatrace_ingest_event. Who changed the configuration: dynatrace_list_audit_logs.
• Security: dynatrace_list_security_problems with status("OPEN"),riskLevel("CRITICAL","HIGH"), then dynatrace_get_security_problem.
• Objectives: dynatrace_list_slos with evaluate: true, dynatrace_get_slo.
• Configuration (read only): dynatrace_list_settings_schemas, dynatrace_get_settings_schema, dynatrace_list_settings_objects, dynatrace_get_settings_object.

Switched off at install: dynatrace_close_problem; it cannot be undone, so an admin switches it on when the team needs it.

Before writing: an ingested alert, error or availability event can open a problem and notify people; comments and tags are visible to everyone in the environment. Confirm with the user first.

Selectors: entity selectors look like type("HOST"),tag("env:prod"),mzName("Production") (criteria joined by commas mean AND; values are case-sensitive); problem, event, SLO and security problem selectors work the same way (status("OPEN"), eventType("CUSTOM_DEPLOYMENT")). Metric selectors chain transformations: builtin:service.response.time:splitBy("dt.entity.service"):avg:sort(value(avg,descending)):limit(10).

Reading the answers: times are UTC milliseconds since 1970 (startTime, endTime, timestamp; -1 means still open). Response times are microseconds, CPU and memory usage percentages, byte counts bytes; get_metric gives the unit. Entity ids look like HOST-1234ABCD5678EF90; the problem id differs from its display id (P-2410123).

Paging: lists return nextPageKey; call again with only next_page_key set (every other filter left out) until it is missing. Log search pages with nextSliceKey (classic log storage only). Keep timeframes short: the default is often the last 2 hours.

Not covered: Grail and DQL queries (<environment>.apps.dynatrace.com/platform/storage/query/v1) need a platform token or OAuth client, not an access token. For those use the Dynatrace Remote MCP server (https://<environment-id>.apps.dynatrace.com/platform-reserved/mcp-gateway/v0.1/servers/dynatrace-mcp/mcp with a platform token).

Errors: 401 means a wrong, expired or revoked token (or a platform token sent here), 403 a token without the scope the call needs (the message names it), 404 an unknown id or a wrong environment address, 400 a malformed selector (the message says where), 429 the rate limit (wait and retry).