Skip to main content

Dashboards (custom analytics)

Dashboards let you assemble your own Explore queries into a saved, arrangeable board. Each dashboard has a title and description and holds any number of visuals — a saved query plus its chart type and grid placement. Visuals load independently, so a slow query never blocks the rest of the board.

Open the list from Monitor > Analytics > Dashboards.

Same datasets as Explore

Dashboards query the same store as Explore, so their visuals can only use the datasets Explore offers for your read store. On PostgreSQL that is Gateway activity (audit logs) only; the other datasets need ClickHouse. On-prem, see Bring your own ClickHouse.

Create and manage dashboards​

  • New dashboard — create a dashboard with a title and description.
  • Edit — rename or re-describe a dashboard, add or remove visuals, and rearrange the grid.
  • Delete — remove a dashboard from the list.

Dashboards are stored per organization, so everyone with access to Analytics sees the same boards.

Add visuals​

From a dashboard in edit mode, choose Add visual. The visual editor is the same query surface as Explore, so you can build each visual with either the guided Query Builder or the WQL console, with a live preview. For each visual you set:

  • Its query (metric, group by / over time, filters, visualization, limit).
  • Its width — one or two columns of the dashboard grid.
  • A title and optional description.

In edit mode, drag and drop visuals to reorder them and change their column span. Each visual fetches its own data when its query changes.

Logs visuals​

When your deployment's logs are in ClickHouse, Add visual has an Analytics query | Logs switch. Choose Logs to show a table of individual log events instead of a chart. Pick a preset or one of your saved views under Start from a view, refine it with the filter bar, and set the order and how many rows load at a time. The switch appears only when you add a visual, so an existing visual keeps its type.

A logs visual follows the dashboard's time range unless you clear Use the dashboard's time range and pick its own. Its Open in Logs button opens the same filters in Logs. Without ClickHouse the Logs option is not offered, and an existing logs visual shows "Logs need ClickHouse".

Dashboard filters and variables​

A dashboard can define dashboard-level filters — a shared control bar that re-scopes the whole board from one place. There are two kinds:

  • Time range — a shared preset or custom start/end range.
  • Field filters (variables) — named values such as a group, source, or user.

How variables apply​

Each field filter has a name (referenced as $name) and can hold either a single value or a list:

  • Single applies with equality (=).
  • List applies with membership (in).

Dashboard filters reach your visuals two ways:

  1. Automatically — a dashboard field filter is applied to every visual whose dataset exposes that column and that does not already set it.
  2. Explicitly — reference a variable inside a visual's query. In the builder, pick "use dashboard variable" as a filter value; in WQL, write it as the value, for example where group = $group. Explicit references win over the automatic pass.

The time range parameter​

Treat the dashboard's time range as a parameter that visuals can opt into:

  • In the builder, choose Dashboard time range for a visual to follow the board's shared range.
  • In WQL, write from $timeframe.

A visual bound to $timeframe inherits the dashboard range; a visual with its own dates keeps them. As with Explore, relative ranges stay dynamic and are resolved each time a visual runs.

What to do next​

  • Explore: build the queries that become dashboard visuals
  • Analytics: the prebuilt analytics dashboard
  • Logs: inspect the individual events behind a trend