Skip to main content
Dynatrace connects to RubixKube today through the custom integrations path. There is no separate prebuilt app to install. Most teams start with Custom REST and move to Custom MCP when they want richer, semantic tools.

​
What to bring in

The signals that matter most when agents are investigating or writing RCAs:
  • Problems (/api/v2/problems) to surface active problems as insight candidates.
  • Entity health (/api/v2/entities) for service, host, and process group state.
  • Metrics (/api/v2/metrics/query) for any metric Dynatrace is holding.
  • Events (/api/v2/events) for deploy markers, config changes, and availability events.
Read-only API tokens are enough for all of the above.

​
Which path to pick

Start with REST

Dynatrace exposes OpenAPI for its Environment API. Upload, enable read endpoints, done.

Move to MCP when you need more

Wrap multiple calls behind named tools (for example dynatrace_entity_health).

​
Quick recipe: REST path

1

Create a Dynatrace API token

In Dynatrace, create a token with entities.read, metrics.read, problems.read, and events.read scopes. No write scopes required.
2

Register the spec

In the RubixKube console, go to Integrations → Custom REST and upload the Dynatrace Environment API OpenAPI spec.
3

Enable the endpoints you care about

Start with problems, entities, and metrics query.
4

Set auth

Add the API token to the workspace secret vault. Map it to the Authorization: Api-Token <token> header.
5

Scope to skills

Attach the enabled endpoints to the skills that need Dynatrace context.
Once connected, the integration is tenant-wide.

​
Example tools worth having

  • dynatrace_active_problems(service) — returns active problems affecting a given service.
  • dynatrace_entity_health(entityId) — returns availability, error rate, and response time for an entity.
  • dynatrace_metric(metric, window) — wraps metric query with a common default window.
  • dynatrace_recent_events(service, window) — returns deploy and config change events for the service.
Define these as skills (or as MCP tools if you want them to compose multiple calls).

Custom REST Integrations

The full REST flow with auth options and approval rules.

Custom MCP Servers

When you want richer tool schemas and multi-call workflows.

Skills

How to compose Dynatrace queries into custom workflows.