Use a gauge to visualize a single numerical value as a gauge.

The gauge visualization above is based on the following query, which calculates CPU as the average host CPU usage. In the Data mapping settings, Gauge value is then set as CPU.
timeseries avg(dt.host.cpu.usage)| fieldsAdd CPU = arrayAvg(`avg(dt.host.cpu.usage)`)| fieldsKeep CPU
The Visual tab settings are as follows:
| Section | Settings |
|---|---|
Data mapping |
|
Gauge bar |
|
Color |
|
Units and formats |
|

The gauge visualization above is based on the following query, which calculates pctActive as the percentage of total problems that are open. In the Data mapping settings, Gauge value is then set as pctActive.
fetch dt.davis.problems| summarize count = count(), by:{event.status}| summarize { active=toDouble(takeAny(if(event.status=="ACTIVE", count))), closed=toDouble(takeAny(if(event.status=="CLOSED", count)))}| fieldsAdd total = active + closed| fieldsAdd pctActive = (active / total) * 100| fieldsKeep pctActive
The Visual tab settings are as follows:
| Section | Settings |
|---|---|
Data mapping |
|
Gauge bar |
|
Color |
|
Units and formats |
|
Use the title field at the top of the options panel (initially Untitled tile or Untitled section) to add a title to your dashboard tile or notebook section.
Example:
Status and Emoji in your dashboard.Current $Emoji status is $Status.Status to Good.Emoji to π.The title will be displayed as Current π status is Good.
If you aren't sure that you chose the right visualization, use the visualization selector to try different visualizations.
The data mapping section shows how a column of your result is mapped to the visualization.
Expand the Data mapping section of your visualization settings to see how data in your result is mapped to your visualization, and to adjust those settings if needed.
Mandatory fields are marked with an asterisk (*). Example:

Data types are displayed next to field names in dropdowns and mapped fields.
Units are displayed when thereβs only one assigned.
Result fields are grouped into Suitable and Unsuitable. Fields are marked as unsuitable if they cannot be used to display data in the visualization. Example:

Automatic application of data mapping default settings:
Dynatrace version 1.319+
For a gauge chart, the data mapping section includes:
Show label: To display a string in the center of the gauge, turn on Show label and enter the string.
Show icon: To display an icon next to the value, turn on Show icon and select an icon from the list.
Min value determines where the gauge starts on the left.
Max value determines where the gauge ends on the right.
100, the right end of the gauge = 100100, the right end of the gauge is the gauge valueThe color settings for a visualization are displayed in rows.
Each row associates a color scheme with a condition/value related to a selected field displayed in the visualization.
To adjust the settings for a row, there are two menus of settings that will be used in combination to determine which color is displayed:
#134FC9) or use the color picker to select a color visually.Move up and Move down move the row up or down one row. These are alternatives to .
Remember that colors are applied in the order in which they are listed in the Colors section, from top to bottom, so changing the order may give you different results.
Duplicate creates a copy of the selected row.
Delete section removes the row. You can delete all color rules for table and single value visualizations; all other visualizations need at least one color rule.
In this pie visualization example, we have applied:
If you changed the order of the rows in the Colors section, you would see different colors. For example, if you swapped rows 2 and 3 above, all slices with values at or above 20 would be colored red, but then all slices with values at or above 15, including all the red slices, would be colored yellow.

In this honeycomb visualization example, we have applied:
value.A values.value.A values at or above 15.value.A values at or above 20,The result is a fully thresholded honeycomb chart. You can use other honeycomb visualization settings to adjust the labels, tooltip, legend, and so on.

To override the default units and formats in a dashboard or notebook visualization
Select to edit the visualization tile.
Select the Visual tab.
Expand Units and formats.
The Units and formats section lists all available unit settings for the document (dashboard or notebook). Some units may already be added automatically when querying metrics from their metadata.
Each row has two menus:

To edit unit settings, open the left menu and review/set the following settings:
Unit: The base unit in which the values were captured. It's None if it was not included in the DQL result, or its automatically defined by the unit passed from the DQL result. This field doesn't lead to any conversion but modifies the suffix to correspond to the unit.
Convert: You can turn on Convert for conversion. For example, if the DQL result defined your numeric value in the result as Bytes, Convert now offers a suitable list of byte conversions such as Kilobyte and Megabyte.
Only linear and static conversions are supported. For example, you cannot convert Degree Celsius(Β°C) into Degree Fahrenheit(Β°F), or convert Usd(US$) into Eur(β¬).
The Format section determines how the unit is displayed:
1053 becomes 1.1K.90 seconds becomes 1m 30s if multiple units is enabled and 2 units are selected.To choose a different field for a row, open the right menu in that row and select a field from the available fields.
This example uses a line chart, but the options apply to other visualizations.
In
Dashboards, create a dashboard.
Select and, in the Library section of the menu, select Chart average CPU across all hosts.
In the edit panel, select the Visual tab and select Line.
Expand Units and formats.
One row is already defined based on metadata from avg(dt.host.cpu.usage).
To override the unit settings for that field, open the left menu in that row to display the unit settings.
Define an override for the displayed metric. You can observe your changes in the Y-axis of the chart.
Unit displays Percent, which is the default unit for the selected metric.
Turn on Convert to try conversions settings. For example, change Auto to One to display the result as a fraction of 1.
Decimals displays the default number of decimal points (degree of precision) to display. For example, enter Pct and review the dashboard to see Pct instead of % displayed after the percentage value.
Turn on Custom suffix to try different suffixes to display after the unit. For example, change the Decimals selection and review the dashboard to see the change in the number of decimal points in the percentage value.
To reset to defaults (discard override settings for the selected metric), open the (Actions) menu for that row and select Reset.
Use the Query limits section to check and adjust the Grail query limits per notebook section or dashboard tile. These settings determine the maximum limits when fetching data. Exceeding any limit will generate a warning.
Dashboard tiles and notebook sections created in Dynatrace earlier than version 1.296 are not affected. Those existing tiles/sections will return the same results as before.
Read data limit (GB)
The limit in gigabytes for the amount of data that will be scanned during a read.
Record limit
The maximum number of result records that this query will return. Default: 1,000 records. To see more records, you need to increase the value of Record limit.
If your query has no limit, such as
fetch logs
the value of Record limit is applied. By default, you will see up to 1,000 records.
If your query also includes a limit, such as
fetch logs| limit 2000
the lower of the two values (either limit in your query, or Record limit in the web UI) is applied.
In the example above, you would still see only 1,000 records unless you increased the value of Record limit.
Result size limit
The maximum number of result bytes that this query will return. For better performance with typical queries and smaller documents, the default is set to 1 MB.
Sampling (Logs and Spans only)
Results in the selection of a subset of Log or Span records.