Skip to main content
The Custom Dashboards page lets you build project-shared dashboards from governed SQL queries and visualizations. You create a dashboard, query your data with SQL against the platform tables, and save each visualization as a widget, every dashboard is shared across the project. Navigation: ProjectCustom Dashboards Date range: Set at the top of the dashboard, for example Last 7 days. Widgets that use the from and to date tokens follow this range, all applicable widgets update. When a project has no dashboards, the page shows No dashboards yet. Select New dashboard to create your first one. Customer Dashboards

Dashboard actions

ActionDescription
New dashboardCreates an empty dashboard that you name and populate with widgets.
ImportLoads a dashboard definition from a file.
ExportSaves the selected dashboard’s definition to a file, so you can move it between projects or keep a backup.
RefreshRe-runs the queries behind the dashboard’s widgets and redraws them with the latest data.
EditOpens the dashboard for changes, such as adding, arranging, or removing widgets.
Time rangeSets the dashboard date range that date-scoped widgets follow.

Build a widget

Each visualization on a dashboard is a widget. You build a widget in the widget editor, which opens as Untitled widget with three tabs.
TabWhat you do
Query dataPick a table and write the SQL that returns your data.
Preview rowsInspect the rows the query returns before you visualize them.
VisualizeTurn the result set into a chart and configure how it displays.
To build a widget:
  1. Open a dashboard and start a new widget.
  2. On Query data, select a table from the table list, for example abl_platform.platform_events.
  3. Write your SQL, or use Columns to insert column names. Select Run query to test it.
  4. Open Preview rows to confirm the query returns what you expect.
  5. Open Visualize and choose how to display the result set.
  6. Select Save widget. To discard your changes, select Cancel.

Example of Query scoping

The platform scopes queries to the current tenant and project by default. Let us consider abl_platform.platform_events as the query table. Use the date tokens when a widget should follow the dashboard date range.
TokenDescription
{tenantId:String}Scopes the query to the current tenant.
{projectId:String}Scopes the query to the current project.
{from:DateTime64(3)}Start of the dashboard date range.
{to:DateTime64(3)}End of the dashboard date range.
The following query counts events over time and follows the dashboard date range:
SELECT
  timestamp,
  count() AS rows
FROM abl_platform.platform_events
WHERE tenant_id = {tenantId:String}
  AND project_id = {projectId:String}
  AND timestamp >= {from:DateTime64(3)}
  AND timestamp <= {to:DateTime64(3)}
GROUP BY timestamp
ORDER BY timestamp DESC
LIMIT 100