Skip to content

Repo sync for protected branch #2927

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
learn-build-service-prod merged 3 commits into from
Aug 6, 2026
Merged

Repo sync for protected branch #2927

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
35aeff8
ADX Dashboard specific visuals - Stat and Multi Stat (#7581)
hzargari-ms Aug 6, 2026
e5a082f
Merge pull request #7583 from MicrosoftDocs/main
learn-build-service-prod[bot] Aug 6, 2026
72a519f
Merging changes synced from https://github.com/MicrosoftDocs/dataexpl…
Aug 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
71 changes: 3 additions & 68 deletions data-explorer/dashboard-visuals.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,80 +3,15 @@ title: Dashboard-specific Visuals
description: Visualizations available in Azure Data Explorer web UI or dashboards
ms.reviewer: gabil
ms.topic: how-to
ms.date: 02/02/2026
ms.date: 08/06/2026
---

# Dashboard-specific visuals

All visualizations that you create in the context of the [render operator](/azure/data-explorer/kusto/query/render-operator) are available in dashboard visualizations. However, the following visualizations are only available in [Azure Data Explorer dashboards](azure-data-explorer-dashboards.md), Real-Time Dashboards, or [Azure Data Explorer web UI](/azure/data-explorer/add-query-visualization), and aren't available by using the render operator.

To learn how to customize any dashboard visuals, see [Customize Azure Data Explorer dashboard visuals](dashboard-customize-visuals.md)
To learn how to customize any dashboard visuals, see [Customize Azure Data Explorer dashboard visuals](dashboard-customize-visuals.md).

For general information on dashboards in Azure Data Explorer, see [Visualize data with Azure Data Explorer dashboards](azure-data-explorer-dashboards.md).

## Funnel chart

A funnel chart visualizes a linear process that has sequential, connected stages. Each funnel stage represents a percentage of the total. In most cases, a funnel chart is shaped like a funnel, with the first stage being the largest, and each subsequent stage smaller than its predecessor.

The following example visualizes the progression of server requests, showing the total number of sessions, requests, and their completion status. It highlights the drop-off from sessions to requests and the proportion of completed versus incomplete requests.

### Example query

```kusto
let stageOrder = datatable(Stage:string, Order:int)
[
"session_id", 1,
"request_id", 2,
"Completed", 3,
"Incomplete", 4
];

let base = TransformedServerMetrics
| where MetricType == "sqlserver_requests";

// Build the funnel table dynamically
let funnelData =
union
(base | where SQLMetrics == "session_id" | summarize Count = count() | extend Stage = "session_id"),
(base | where SQLMetrics == "request_id" | summarize Count = count() | extend Stage = "request_id"),
(base | where SQLMetrics == "percent_complete"
| summarize Count = countif(Value == 100) | extend Stage = "Completed"),
(base | where SQLMetrics == "percent_complete"
| summarize Count = countif(Value < 100) | extend Stage = "Incomplete");

// Join with stage order and order properly
funnelData
| join kind=inner stageOrder on Stage
| order by Order asc
| project Stage, Count
```

:::image type="content" source="media/adx-dashboards/funnel.png" alt-text="Screenshot of a funnel chart visualizing server requests.":::

## Heatmap

A heatmap shows values for a main variable of interest across two axis variables as a grid of colored squares.

To render a heatmap, the query must generate a table with three columns. The data used for the value field must be numeric. The columns that you use for x and y values must follow these rules:

- If the values in column *x* are in the `string` format, the values in the column *y* must also be in the `string` format.
- If the values in column *x* are in the `datetime` format, the values in the column *y* must be numeric.

> [!NOTE]
> Specify each data field instead of letting the tool infer the data source.

The following example shows the distribution of the five most frequent SQL metrics across different metric types. It highlights which metric types are most common for each SQL metric, making it easy to identify activity patterns in the top metrics.

### Example query

```kusto
let topMetrics = TransformedServerMetrics
| summarize TotalCount = count() by SQLMetrics
| top 5 by TotalCount; // pick only the 5 most common metrics
TransformedServerMetrics
| where SQLMetrics in (topMetrics | project SQLMetrics)
| summarize Count = count() by SQLMetrics, MetricType
| project X = MetricType, Y = SQLMetrics, Value = Count
```

:::image type="content" source="media/adx-dashboards/heatmap.png" alt-text="Screenshot of a heatmap visualizing server metrics.":::
[!INCLUDE [dashboard visuals](includes/cross-repo/dashboard-visuals.md)]