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 plug your own content into these experiences, or define entirely new ones, by shipping documents. Documents are 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 Infrastructure & Operations (from version 1.25.0). Target your documents at it to make your content available immediately. 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, and others), 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 terms to keep in mind:

Definition documents own a whole layout: use them to create a page or an 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 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: Look up the four document shapes and their fields.
Targeting: Control which app, entity type, or Inventory Explorer instance a document applies to using target.
Conditional rendering: Show or hide parts of a document at runtime based on DQL query results.
Elements overview: Explore what can go inside a document's content: layouts, cards, and built-in references.
Element reference: Look up property-by-property details for each element type (DQL table, Chart group, Filtering, Metadata, Message, and more).
Deploy an extension with UA page documents: Deploy UA pages with an extension in a simple end-to-end example.