After you run a Data Explorer query, use the result visualization to investigate its data, save it to a dashboard, or share and export the query results.
The Result section displays the selected visualization of your query results.
You can hover over and select visualization elements to view details, drill down to relevant Dynatrace pages, and alter the visualization to help you identify problems.
In this example, a Graph visualization shows a line chart of the CPU usage % metric for hosts. One host behaves erratically, so selecting it opens a popup with details about the host.

In this example, you have the following options:
The options available in the popup depend on the query and visualization you configured.
To temporarily remove potential clutter from your graph and focus on a single metric, you can hide everything but a selected metric series.
Graph visualization.On a line graph, select the line for the metric you want to focus on.
In the popup, select Focus.
The graph is redrawn with only the selected metric displayed.
On the graph, select the line for the metric you have focused on.
In the popup, select Remove focus.
The graph is redrawn to display all metrics.
To help you identify anomalies, you can use baselining to add a confidence band to a metric's line on the chart. Then you can see when the value goes outside the confidence band. The baseline calculation is based on the Seasonal baseline model which is used to create metric events for anomaly detection.
Baselines apply only to the Graph visualization.
Baselines aren't added to the dashboard tile when you pin a chart to a dashboard.
The timeframe used to infer the baseline is determined by the currently selected resolution:
| Resolution range | Resolution examples | Baseline timeframe |
|---|---|---|
resolution < 5 minutes |
| previous 14 days |
5 minutes ≥ resolution < 1 hour |
| previous 28 days |
1 hour ≥ resolution < 1 day |
| 400 days |
resolution ≥ 1 day |
| 5 years |
Loading). The graph is then redrawn with the baseline displayed for the metric you selected.Baselines are listed separately in the chart legend. For example, if you add a baseline to the CPU usage % metric in a Graph visualization, the legend lists CPU usage % and CPU usage % - baseline. Select the legend entries to toggle their display on or off.
You may notice differences between baselines in Data Explorer and metric events. These features offer different approaches to suit their different contexts. In general, the Data Explorer configuration is fixed, while the metric events configuration is configurable.
| Data Explorer | Metric events | |
|---|---|---|
Samples |
| Configurable |
Violating samples |
| Configurable |
Dealerting samples |
| Configurable |
Alert on no data |
| Configurable |
Tolerance (affects width of confidence band) |
| Configurable (range: |
Resolution (affects granularity) | Configurable |
|
Training time | Instantaneous | Daily |
For details on seasonal baselining, see Seasonal baseline.
The baseline calculation is based on the seasonal baseline model used to create metric events for anomaly detection. For details on the inner workings of the model, see Seasonal baseline.
Although the baseline model is based on the seasonal baseline model, there are several reasons why the resulting baselines can differ:
Dynatrace Davis® takes domain-specific knowledge and topology into account when computing connected observability signals. Davis ranks the most relevant signals on top, and the Davis score for each detected signal indicates how closely the signal matches the reference signal's behavior during the selected timeframe. More about Davis® AI.
Note that this option is available only if you Split by a dimension in the query.
Go to Data Explorer (standard or advanced mode), create a query of a metric series split by a related dimension, and display it in the Graph visualization.
Correlated metrics are available only if you:
Graph visualizationTry this example:

That's this in Advanced mode:

builtin:host.cpu.usage:splitBy("dt.entity.host"):sort(value(auto,descending)):limit(20)
Select Run query to graph the query.
Select a line on the graph to display a popup of related options.
In the popup, select See correlated metrics.
The Davis for Correlation analysis side panel lists metrics that, based on Davis AI correlation analysis, are correlated to the selected series. This correlation is determined by the shape of the series, not the values.
Reference signal represents the data series you selected on the graph. Other shapes of other metric series are compared to the shape of this series.
Connected signals are other metric series that have a similar shape, sorted by most similar to least similar. The more similar the shape, the closer the correlation.
For each correlated metric, the analyzer displays:
Correlations are sometimes grouped.
In the side panel, select any listed metric to automatically add it to your current query.
After you add correlated metrics, select Run query to update the graph.
To determine correlation, the analyzer checks the shape of the data series, not the values. Two series with very similar shapes are correlated.
Possible reasons why you see no "See correlated metrics" option include:
Graph visualizationIf No connected signals found is displayed, possibilities include:
To save the visualization as a dashboard tile, select Pin to dashboard. For details, see Pin tiles to your dashboard.
If you find results that you want to share with authenticated users or revisit with a later timeframe:
To export to a comma-separated values (CSV) file
Go to Data Explorer and, in the Result section, select > Export CSV.
A CSV file of the results is saved to your local machine.
The filename indicates the metrics, date, and timeframe.
For example:
CPU usage % (May 24, 2022, 11_41 - 13_41).csv—contains results from metric CPU usage %, run on May 24, 2022, for a two-hour timeframe of 11:41 AM to 1:41 PM.CPU usage % +1 (May 24, 2022, 13_19 - 13_49).csv—contains results from metric CPU usage % and one more metric, run on May 24, 2022, for a half-hour timeframe of 1:19 PM to 1:49 PM.After you run a query, you have the option to copy the request for use in an API request.
A metric shows 20 series by default and 100 at most, even after you remove the limit transformation in advanced mode. To see the series you need, add more specific filters, such as a management zone or an entity name. If a metric expression returns no series, see Why is the result of my metric expression empty?.
Each metric returns its own top series. For example, if you query builtin:host.cpu.usage and builtin:host.cpu.idle split by dt.entity.host, each metric returns its own top 100 hosts. Hosts that appear in only one result leave empty cells. To align the records, set a global limit.
The Fold transformation setting affects the resolution.
If Fold transformation is set to Auto for visualization Table, Single value, Top list, or Honeycomb, the Inf (infinity) resolution is used to maintain backward compatibility. If the chosen metric selector doesn't support the Inf resolution, the fold transformation is automatically added to the end of the query.
If Fold transformation is set to a value other than Auto, fold is used.
Because all metric selectors are queried using the same total value mechanism (either fold or Inf), adding a new selector that requires fold might change the result of the other selectors.
To inspect the actual query used by Data Explorer, go to the Result section in Data Explorer and select > Copy request.
The metrics builtin:host.availability and builtin:pgi.availability are based on time-series data provided by OneAgent. Dedicated events calculate the availability values shown on the Hosts and Processes pages, so the values can differ.
In the future, the availability shown on the Hosts and Processes pages will also be based on the availability metrics.
If a chart shows a misleading drop in values at the end of the current timeframe, manually subtract the last one or two time buckets from the timeframe.
To temporarily adjust the timeframe:
-2h to -2h-2m.To set the adjusted timeframe as the default for a dashboard:
-2h to -2h-2m.For a discussion of this behavior, see Correction required on Dashboard Charts showing dip at current time in the Dynatrace Community.
For more information, see timeframes.