Unified analysis on Platform

Latest Dynatrace
Overview
3-min read
Published Jul 13, 2026

Many Dynatrace apps — such as Infrastructure & Operations, Kubernetes, and Services — present your monitored entities through unified analysis (UA). As an extension developer you can plug your own content into these experiences, or define entirely new ones, by shipping documents: JSON configurations that the app picks up and renders at runtime.

Supported Apps

Document-based extension UA pages are rolling out to apps gradually. The first app to support it is the Infrastructure & Operations app (dynatrace.infraops) from version 1.25.0 — target your documents at it to have your content picked up today. Support in further apps will follow.

The two UA experiences

Inventory Explorer — a browsable, filterable list of all entities of a given type (for example, every host or every database), with a details panel for whichever entity is selected.
Entity Details — a view for a single entity, with a header, tabs, and cards showing its data, health, relationships, and more.

Both experiences are assembled from elements — cards (tables, charts, properties, messages…), layouts, and filters. A document describes which elements appear and how they're arranged.

A complete entity-type experience is usually a pair of documents: an InvExTypeDefinition for the browsable list, and an EntityDetailsDefinition for the per-entity details opened from it. They are separate documents, wired together by node type.

What a document can do

Every document declares a type that says what it does and where it applies:

Type	What it does
`EntityDetailsDefinition`	Defines the full Entity Details page (header, tabs, cards) for an entity type.
`EntityDetailsInjection`	Adds a tab or a card into an Entity Details page the app already provides.
`InvExTypeDefinition`	Adds a new type (or subtype) to Inventory Explorer.
`InvExInjection`	Adds content into an Inventory Explorer type the app already provides.

Two verbs to keep in mind:

Definition documents own a whole layout — use them to create a page or an Inventory Explorer type from scratch.
Injection documents add to a layout that already exists — use them to enrich an app's built-in experience with your own cards or tabs.

A document is fetched at runtime based on its target — the app and entity type it applies to — so your content shows up wherever it's relevant without any coordination with the app.

Bundling a document with an extension

Documents can be delivered with extensions by declaring them in the documents.screens section of the extension.yaml file. For example:

name: custom:my-extension
version: 1.0.0
minDynatraceVersion: "1.343"
author:
  name: Joe Doe

documents:
  screens:
    - path: screens/my-ua-screen.screen.json

Documents declared in this way are uploaded to Dynatrace when the extension is installed, and cleaned-up when the extension is removed.

A minimal example

This injection adds a card to the "overview" tab of the Entity Details page for hosts:

{
  "version": "1.3.0",
  "type": "EntityDetailsInjection",
  "target": {
    "app": "dynatrace.infraops",
    "nodeType": "dt.entity.host",
    "tabId": "overview"
  },
  "content": {
    "type": "message",
    "id": "my-welcome-card",
    "cardTitle": "Welcome",
    "content": "This card was injected from a document."
  }
}

Save this document as a JSON file screens/my-injection.screen.json and ship it with your extension by declaring it in your extension.yaml file:

name: custom:my-extension
version: 1.0.0
minDynatraceVersion: "1.343"
author:
  name: Joe Doe

documents:
  screens:
    - path: screens/my-injection.screen.json

Where to go next

Document types — the four document shapes and their fields.
Targeting — how a document's target decides which app, entity type, or Inventory Explorer instance it applies to.
Conditional rendering — how to show or hide parts of a document at runtime based on DQL query results.
Elements overview — what can go inside a document's content: layouts, cards, and built-in references.
Element reference — full property-by-property reference for each element type (DQL Table, Chart Group, Filtering, Metadata, Message, and more).
Deploy an extension with UA page documents — simple end-to-end example of how to deploy UA pages with an extension.