Study guide

15.2 Dashboards: Tiles, Variables, Segments & Continuous Monitoring

Dynatrace Certified Associate Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Overview, Deployment Models & Architecture

1.1 Dynatrace Platform Capabilities, Web UI Navigation & the Dynatrace Hub 1.2 SaaS vs. Dynatrace Managed Architecture & Security 1.3 Core Telemetry Components: OneAgent, ActiveGate & Grail Lakehouse 1.4 Licensing Models: Dynatrace Platform Subscription (DPS) & Davis Data Units (DDUs)

2 Chapter 2: ActiveGate Architecture & Network Topologies

2.1 ActiveGate Types: Environment vs. Cluster ActiveGates 2.2 ActiveGate Capabilities: Proxying, Private Synthetic, Cloud Integrations & Extensions 2.3 Network Zones, Multi-DC Routing & Firewall Traversal

3 Chapter 3: OneAgent Deployment, Configuration & Management

3.1 OneAgent Architecture, Components & Automatic Injection 3.2 Host Installation on Linux, Windows & Containerized Hosts 3.3 Cloud-Native Deployment: Dynatrace Operator on Kubernetes & OpenShift 3.4 Kubernetes Observability: Clusters, Nodes, Namespaces, Workloads & Events

4 Chapter 4: Monitoring Modes, Process Groups & Infrastructure Observability

4.1 Monitoring Modes: Full-Stack vs. Infrastructure-Only vs. Discovery 4.2 Process Groups, Process Instances & Custom Process Group Detection Rules 4.3 Host Groups, Host Naming Rules & Environmental Metadata Extraction 4.4 Infrastructure & Operations: Host Health, Disk, Network & Availability Analysis 4.5 Database Observability: The Databases App, Connection Pools & Storage Latency

5 Chapter 5: Smartscape Topology & Service Flow

5.1 The 5-Layer Smartscape Topology: Datacenter to Application 5.2 Service Detection: Web Services, Background Tasks & Custom Services 5.3 Service Flow, Backtrace Analysis & Horizontal/Vertical Dependency Mapping

6 Chapter 6: PurePath Distributed Tracing & Code-Level Diagnostics

6.1 PurePath Architecture, Distributed Tracing & Request Context Propagation 6.2 Method Hotspots, CPU Profiling & Memory Allocation Thread Analysis 6.3 Database Service Diagnostics, Slow Queries & Exception Analysis

7 Chapter 7: Davis AI Engine, Baselining & Causation

7.1 Davis Deterministic Causation Engine vs. Pure Correlation 7.2 Automated Dynamic Baselining, Percentiles & Traffic Seasonality 7.3 Event Ingestion, Event Types & Event Hierarchy in Problem Evolution

8 Chapter 8: Problem Lifecycle, Root Cause Analysis & Alerting

8.1 Problem Lifecycle, Severity Categories & Root Cause Cards 8.2 Alerting Profiles, Delay Filters & Management Zone Routing 8.3 Problem Notification Integrations: Webhooks, Slack, ServiceNow & ITSM

9 Chapter 9: Digital Experience Monitoring: Synthetic Monitoring

9.1 Synthetic Monitors: HTTP, Single-Step Browser & Multi-Step Clickpaths 9.2 Private Synthetic Locations, ActiveGate Engines & Credential Vault 9.3 Outage Detection, Performance Baselining & Maintenance Suppression

10 Chapter 10: Digital Experience Monitoring: Real User Monitoring (RUM)

10.1 RUM Architecture, OneAgent Script Injection & Mobile/OpenKit Telemetry 10.2 User Actions: Load vs. XHR/Fetch Actions, Visually Complete & Speed Index 10.3 Apdex Performance Ratings, User Sessions & Session Replay Masking

11 Chapter 11: Log Management and Analytics on Grail with DQL

11.1 Log Management on Grail: Storage, Ingestion Pipelines & Log Masking 11.2 Dynatrace Query Language (DQL): Fetch, Filter, Fields & String Operations 11.3 DQL Aggregations: Summarize, MakeTimeseries, Sorting & Visualizations

12 Chapter 12: Platform Governance, OpenTelemetry & Automation

12.1 Management Zones: Scoping Observability, Dashboards & Access Control 12.2 Tagging Strategies: Automated Rule-Based Tags, Manual Tags & AWS/K8s Metadata 12.3 OpenTelemetry Ingestion, OpenPipeline & Dynatrace Workflows Automation

13 Chapter 13: Cloud Integrations & Agentless Infrastructure Ingestion

13.1 AWS, Azure & Google Cloud Integrations 13.2 VMware vSphere, Extensions & Other Agentless Ingestion Paths

14 Chapter 14: Business Analytics & Business Events

14.1 Business Events: Capture, Ingestion & the bizevents Grail Table 14.2 Business Analytics: Connecting Performance to Revenue, Conversion & KPIs

15 Chapter 15: Notebooks, Dashboards & Data Visualization

15.1 Notebooks: Section-Based Investigation & Shareable Analysis 15.2 Dashboards: Tiles, Variables, Segments & Continuous Monitoring 15.3 Choosing Visualizations: Data Explorer, Chart Types & Metric Selection

16 Chapter 16: Reporting, Metrics & User Behavior Analysis

16.1 Metrics on Grail: Built-in Metrics, Granularity & Retention 16.2 Dashboard Reports, Subscriptions & Exporting Data via APIs 16.3 User Behavior Analysis: Bounce Rate, Landing & Exit Pages, Conversion Goals 16.4 Session Segmentation, User Journeys & Funnel Drop-Off Analysis

17 Chapter 17: Security, Vulnerability Analytics & Application Protection

17.1 Platform Security: Data Privacy, Encryption & Access Control 17.2 Third-Party Vulnerabilities, the Davis Security Score & Security Advisor 17.3 Code-Level Vulnerabilities, Attacks & Runtime Application Protection 17.4 Security Investigator, Notifications & the Remediation Workflow

15.2 Dashboards: Tiles, Variables, Segments & Continuous Monitoring

Key Takeaways Explain This Topic AI

A dashboard consists of tiles, and the four tile types are Explore, Query, Code, and Markdown.

Explore tiles use a point-and-click interface over logs, metrics, and business events; Query tiles display data returned by a Grail query.

Variables make one dashboard serve many contexts, and the four variable types are DQL, Code, List, and Free Text.

Variables can filter the dashboard, supply values to code tiles, and act as placeholders in tile titles and markdown text.

Custom segments can be enabled per tile from the tile edit panel, letting a single dashboard be re-scoped without duplicating it.

Last updated: September 2026

A dashboard is the platform's continuous monitoring surface. Section 15.1 established when to reach for it; this section covers how it is built, because the exam asks about tile types, variables, and segments by name.

Dynatrace's own positioning: "Dashboards are a cornerstone of the Dynatrace Platform, offering visual interfaces that provide real-time insights into application and infrastructure performance. By aggregating key metrics and data in a clear, customizable format, dashboards allow users to monitor, analyze, and troubleshoot issues."

The Four Tile Types

A dashboard consists of multiple tiles, and each is one of four kinds:

Tile type What it does When to use it

Explore Explore data such as logs, metrics, and business events with a point-and-click interface Fast tile creation without writing DQL; ideal for less technical builders

Query Displays data queried via Grail using DQL Anything the point-and-click builder cannot express

Code Displays data returned by code executed via Dynatrace functions External sources, custom transformations, blended data

Markdown Static content edited in markdown Titles, section headers, runbook links, escalation contacts

The Explore-versus-Query distinction is the one exam questions target. Explore is a guided builder; Query is raw DQL. A scenario describing a business analyst who must add a tile without learning DQL is answered with Explore .

The Markdown tile is under-appreciated in practice and worth remembering: putting the on-call escalation path and the runbook link directly on the dashboard is what makes it usable at 3 a.m.

Variables: One Dashboard, Many Contexts

Without variables, organizations duplicate a dashboard per team, per environment, and per region, and the copies drift apart within weeks. Variables solve this. Use variables to filter your dashboards, to act as variable values in code tiles, and as placeholders in tile titles and markdown tile text.

Those three uses are worth memorizing individually, because the placeholder capability is the one candidates forget: a tile titled Error rate — $namespace renames itself as the viewer changes the selection, so the dashboard never lies about what it is showing.

There are four variable types:

Type Value comes from Typical use

DQL The value is returned from a query A live list of namespaces, services, or hosts that stays current automatically

  • Code The value is returned from code A list assembled from an external system, such as a CMDB
  • List A comma-separated values list A short, stable set such as prod,staging,dev
  • Free Text Free text entered by the viewer An order ID, trace ID, or customer identifier

A DQL-backed variable is almost always the better engineering choice over a List variable for anything that changes: a hardcoded list of services silently goes stale the moment a new service is deployed, whereas the query-backed list picks it up on the next refresh. Exam scenarios that mention "new services keep being missed from the dashboard" are pointing at this.

Segments

Where variables parameterize a query, segments re-scope the data. You turn on Custom segments in the tile edit panel, select a segment from the Custom segments list, and add additional segments to the selected tile for filtering data.

The practical difference:

A variable changes an input to the query — "show me namespace checkout instead of search ."

A segment applies a saved, named scope — "show me the EMEA production estate" — consistently across tiles and reusable across dashboards.

Segments are how a platform team publishes one golden dashboard that each tenant reads through their own scope, which pairs naturally with the management zones covered in Chapter 12.

Designing a Dashboard That Gets Used

The scenarios on the exam usually reward the same design instincts:

One dashboard, one audience, one question. An executive availability board and an SRE debugging board should not be the same artifact.

Lead with the answer. Put the two or three tiles that state overall health at the top; put breakdowns below.

Parameterize instead of duplicating. If you are about to clone a dashboard, add a variable.

Add a markdown tile with the runbook. A dashboard that shows a red tile without saying what to do about it is only half-built.

Only promote validated queries. From Section 15.1 — tiles should come from questions that proved useful in a real investigation.

Drilldowns

A dashboard is an entry point, not a terminus. Tiles support drilldowns into the underlying app — from an error-rate tile into the Logs app with the same filter and timeframe applied, or from a service tile into distributed tracing. The exam framing is that the dashboard tells you that something is wrong and the drilldown carries the timeframe and filter context into the app that tells you why , without the analyst having to rebuild the query by hand.

Loading diagram... Dashboard Anatomy: Tile Types, Variables, and Segments