Track deployed versions with the Release Monitoring dashboard

Latest Dynatrace
How-to guide
5-min read
Published Jun 30, 2026

The Release Monitoring dashboard gives you a real-time view of your deployed software versions, Kubernetes workload alignment, active problems, security vulnerabilities, and CI/CD deployment events in one dashboard, scoped to the releases you care about.

Prerequisites

OneAgent monitors the processes you want to track.
Processes are tagged with the following environment variables at deployment time:
- DT_RELEASE_VERSION (required)
- DT_RELEASE_STAGE (required)
- DT_RELEASE_PRODUCT (required)
To set up version metadata, see Version detection methods.
For Kubernetes sections: Kubernetes monitoring is enabled in Dynatrace. (optional)
For vulnerability data: Dynatrace Application Security is enabled. (optional)
For SDLC events: deployments are reported via the SDLC Events API. (optional)

Filter the dashboard

Open the Release Monitoring dashboard.
Use the Stage filter to select the environment (for example, production).
Optionally narrow the results by Product and Version.
For Kubernetes workloads, apply Cluster and Namespace filters to focus your view.

The filters are cascading: Stage determines which products appear, Product determines which versions appear, and Cluster determines which namespaces appear.

The HostGroup filter applies only to the Non-K8s Processes table and does not affect Kubernetes or SDLC event tiles.

Understand the dashboard sections

The dashboard is organized into sections, each covering a different aspect of release health. Use the descriptions below to understand what each tile and table shows and how to interpret the values.

Release Health Overview

The Release Health Overview section shows key release health indicators at a glance.

Tile	What it shows
Distinct Versions Deployed	Number of distinct `DT_RELEASE_VERSION` values running in the filtered scope. Values above 1 per product indicate a rolling deployment or environment drift.
Active Problems — New Today	Problems opened in the last 24 hours on services backed by the filtered release. Turns red at 1. Use the Active Problems — Blast Radius by Service table to investigate.
Critical/High Vulnerabilities	Count of CRITICAL and HIGH CVE findings on the filtered processes. Green at 0, amber at 1–4, red at 5+.
Products with Active Problems	Meter showing how many of your filtered products have at least one active incident.
Service Requests / Service Errors	Request volume and failed request trends over the selected time window. Errors rising while requests stay flat indicate a regression introduced by the deployment.

Kubernetes Workload Release Inventory

Use the Cluster and Namespace filters to narrow the scope.

K8s Workloads — Release Inventory

The K8s Workloads — Release Inventory table shows one row per Kubernetes workload (Deployment, StatefulSet, or DaemonSet), including its release metadata.

Column	Description
`version`	`DT_RELEASE_VERSION` process tag that updates immediately when the process restarts with the new version.
`k8s_container_version`	Container image tag that lags behind during rolling deployments.
`alignment`	Aligned = versions match (rollout complete). Rolling = mismatch, rollout still in progress. Cell background is color-coded: green for Aligned, red for Rolling.

K8s Workloads — Version Alignment

Each cell in the honeycomb represents one workload. Green = rollout complete, red = rolling deployment in progress. Use the honeycomb for a fast fleet-wide status check without scanning the table row by row.

To analyze a workload in more detail, select its row or cell, open the menu, and select Open with.

Non-K8s Processes — Release Inventory

The Non-K8s Processes — Release Inventory table lists processes with DT_RELEASE_VERSION that run outside Kubernetes, such as on VMs, bare-metal hosts, or AWS ECS.

The Type column distinguishes ECS from VM processes. The Group column shows the host group (VM) or ECS container name. Use the HostGroup filter to narrow VM processes; ECS processes are always visible regardless of that filter. To analyze a process in more detail, select its row, open the menu, and select Open with.

Version Drift Across Stages

The Version Drift Across Stages table shows every active product × stage × version combination. Keep Version set to all to see the full picture. Selecting a specific version hides stages that haven't received that version yet. Multiple rows for the same product reveal where a rollout hasn't fully propagated.

Active Problems & Risk Assessment

The first row pairs the Active Problems by Category donut (incident type distribution across AVAILABILITY, ERROR, SLOWDOWN, and more) with the Top 10 Services by Active Problems, a ranked table of the services impacted most severely by active incidents.

Column	Description
`service_name`	Clickable link to the service in Dynatrace InfraOps.
`stage` / `product` / `version`	Release context of the backing process.
`related_process`	The monitored process that backs this service.
`problem_count`	Number of distinct active problems affecting this service.
`problem_ids`	Clickable `[P-XXXXXX](link)` links to each problem, rendered as markdown and line-wrapped per problem.

Active Problems — Blast Radius by Service

The Active Problems — Blast Radius by Service table shows a full problem list, with one row per problem × affected service. A single incident affecting multiple services produces multiple rows, so the row count reflects the blast radius, not the incident count. The Related Process, Version, and Stage columns identify which specific release is involved.

Select any problem ID in the problem_ids column to open it directly in Problems app - new Problems.

Vulnerabilities

The first row, Vulnerabilities by Risk Level, shows the overall severity mix in a donut, alongside Top 10 Processes by Vulnerability Count, a ranked table of processes with the most open CVEs.

Column	Description
`process_name`	Clickable link to the process in Dynatrace InfraOps.
`stage` / `product` / `version`	Release context of the process.
`critical` / `high` / `medium` / `low`	CVE counts per severity level. Cell backgrounds are color-coded: red, orange, yellow, blue.
`total`	Total open CVE count (all severities).

The Vulnerabilities Related to Filtered Processes table shows one row per CVE across all filtered processes, sorted CRITICAL first. The processes column lists every affected process as a clickable markdown link. Compare across versions to spot exposures introduced by a specific release.

Column	Description
`vulnerability.id` / `vulnerability.title`	CVE identifier and title.
`vulnerability.risk.level`	CRITICAL / HIGH / MEDIUM / LOW / NONE. The cell background is color-coded.
`affected_processes`	Number of distinct processes exposed to this CVE.
`affected_products` / `affected_versions`	Breadth of impact across products and versions.
`processes`	Clickable `[process name](link)` links for each affected process, rendered as markdown and line-wrapped per process.

To analyze a vulnerability or process in more detail, select its row, open the menu, and select Open with. Select, for example, Application Security for full CVE details or InfraOps for process context.

SDLC Deployment Events

The SDLC Deployment Events section sources its data from the SDLC Events API. The Product and Version filters don't apply here because SDLC events lack a product field. The section shows all events for the selected Stage.

Recent Deployments lists the latest completed deployment events, including name, status, and duration. Deployment Outcomes Over Time shows succeeded vs. failed deployments as an area chart. Spikes in failures correlate with timestamps in Recent Deployments.

To add deep link tiles that go directly from a release row into your issue tracker, see Configure DQL tiles to track release-related issues with deep links.

FAQ

Is my rollout complete?

Check the Distinct Versions Deployed tile. If it shows 1, all processes in scope are on the same version. Go to K8s Workloads — Version Alignment to confirm no workloads are still rolling.

Did this release introduce a problem?

Check Active Problems — New Today and the Service Errors chart. If errors rose after your deployment, cross-reference the timestamp in Recent Deployments to confirm the correlation. Open Top 10 Services by Active Problems to see which services are most affected and select individual problem IDs to go directly to the problem.

Is this version safe to promote?

Check Critical/High Vulnerabilities and the Top 10 Processes by Vulnerability Count table. If new CVEs appear in this version that weren't present in the previous one, or if CRITICAL/HIGH counts are non-zero, investigate before promoting. Use Vulnerabilities Related to Filtered Processes for the full CVE list with per-process links.

Where is version X deployed right now?

Set Version to the specific version and check the Version Drift Across Stages table. Each row shows a stage where that version is currently running.