The dashboards discussed here are classic dashboards created using the dashboarding functionality integrated with previous Dynatrace.
To visualize your query results as a table, one metric per column, select Table
from the list above the query definition, in the upper-left corner of the page.
When switching between visualizations, be aware that some visualization settings are visualization-specific.
If you select a visualization and configure Settings for that visualization, and then you switch to a different visualization, some of your settings for the first visualization may be ignored because they don't apply to the newly selected visualization. An information icon in the list of visualizations will alert you to the possibility.
If you switch back to the original visualization, you may need to reconfigure some visualization settings.
Your visualization can show any selection of metrics in a multi-metric query.
To toggle metrics on and off, you can select the letter next to the metric you want to visualize, or you can select the eye icon .
By default, Data Explorer tables are sorted by the first metric in the table query (in descending order based on the aggregation chosen).
To sort a Data Explorer table by a different column, you need to change the column order.
Locate the metric by which you want to sort the table.
Drag that metric to the top position in the query definition.
Run the query.
The table will be sorted by the metric you dragged to the first place in the query definition.
To set the sort order
Sort by
from the list.ASC
(ascending) or DESC
(descending).The Settings section is one of the expandable sections in the right panel of Data Explorer. The contents of the Settings section may vary depending on the visualization you have selected.
The fold transformation combines a data points list (a timeseries: a collection of data points over the time period) into a single data point.
Auto
, which automatically selects the most appropriate time aggregation based on the metric.Auto
with any of the following: Last value
, Average
, Count
, Maximum
, Minimum
, Sum
, Median
, Value
, Percentile 10th
, Percentile 75th
, Percentile 90th
.Last value
.Be aware that 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.
Table column names are the same as the metric names by default. You can change the name of table column headings. The query definition retains the metric's original name.
To rename a column
In the Settings section, select for the metric/column you want to rename.
Edit the name, and then select the checkmark to save the new name.
Use the Unit and Format settings to determine how your data is displayed. If you export to a CSV file, the Unit and Format settings are also reflected in the exported values.
Use the Unit setting to set the unit in which the metric is displayed.
None
= No unit displayedAuto
= Dynatrace selects an appropriate display unit:setUnit(<unit>)
to select from a wider range of units.Examples of order-of-magnitude notation in Dynatrace:
Notation
Factor
Meaning
k
10^3
kilo, thousand
M
10^6
mega, million
G
10^9
giga, billion
T
10^12
tera, trillion
Use the Format setting to configure the number of decimal places displayed for the selected metric.
None
= No formatting.Auto
= Dynatrace selects an appropriate format. For example, where None
would display 5.062357754177517 %
, Auto
would display 5.06 %
.0
, 0.0
, 0.00
, 0.000
When the basic unit of the metric is bytes:
If you set Unit to Auto
, Dynatrace automatically expresses the results in a human-readable unit, which in this case could be GiB
.
A byte-based unit can have either a binary or decimal base, which will determine whether Dynatrace selects, for example, GiB
or GB
. If no base is defined in the metric itself, a decimal base is used.
If the automatically selected unit isn't suitable in your case, you can force Dynatrace to express the same values in a specific unit (Unit = B
, KiB
, MiB
, or GiB
).
If you want to see raw data (no conversion), you can set Unit to None
and see the results in the basic unit of the metric (which in this case is bytes).
When the basic unit of a metric is dollars and cents:
Auto
, and set Format to 0.00
(to have two decimal places for the cents).k (thousand)
, M (million)
, G (billion)
, and set Format to 0
(to see nothing after the decimal point).When the basic unit for the metric is a count:
To see an exact count:
Auto
None
To see a rough count:
k (thousand)
, M (million)
, G (billion)
, or T (trillion)
, depending on the magnitude of your values0.0
, 0.00
, or 0.0000
, depending on how many decimal places make sense in combination with the selected Unit settingWhen setting threshold values:
MiB
), the Threshold settings are then prepared to match the selected unit, so you just need to enter threshold values without specifying MiB
.Auto
(to let Dynatrace automatically scale the displayed output), you still need to set Threshold values in a specific unit such as bytes.Use the checkboxes in the Columns section of the Data Explorer table visualization to enable and disable columns individually. These selections are reflected in the resulting table dashboard tiles.
In Data Explorer, a maximum of 100 results are returned.
To set an explicit limit
Limit
from the list.To remove the limit from your query, turn on Advanced mode and delete the :limit(n)
component of the query.
In a dashboard table tile, the maximum number of rows displayed is determined by the query limit set in Data Explorer. Results are displayed in pages on the tile.
Use the controls at the bottom of the Result section of a Data Explorer table visualization to page through tables.
To enhance your visualizations, you can set thresholds that are reflected in your visualization.
A table can have as many thresholds as there are metrics displayed on the table. This example has five metrics, five columns, each with a different threshold definition. Link cell color to thresholds is turned on.
Tile text color is adjusted automatically for contrast with the background threshold color.
To make per-metric threshold settings
When this is turned on, the background of every cell in the table is colored according to threshold.
When this is turned off, only the cell data is colored.
Select a metric name
Set the threshold values for that metric
optional Adjust threshold colors
Select Add threshold as needed to add thresholds for another metric.
To hide or show threshold colors (per threshold definition) without deleting the threshold settings, in the Thresholds section, select for that metric.
To delete the threshold settings for a metric, in the Thresholds section, select the trash can icon for that metric.
20
. Consequently, some series might be missing in Data Explorer. To ensure the series data you're looking for is displayed, provide more specific filters such as a management zone or an entity name filter.100
. Note that this limit applies even if you remove the limit transformation from the metric selector on the Code tab.If series data is absent for a metric expression, see Why is the result of my metric expression empty?.
The root cause of this issue is often the same as for Why am I not seeing all series of my metric?
The metric series are limited to a certain number.
Suppose you query builtin:host.cpu.usage
and builtin:host.cpu.idle
split by dt.entity.host
. For both metrics, the top 100 hosts are requested per default. But the top 100 hosts of the builtin:host.cpu.usage
metric probably diverges from the top 100 hosts of the builtin:host.cpu.idle
metric, leading to empty cells in the table for some hosts.