Superset
Embedding Superset dashboards inside AccelerUp.
Data Warehouse → Superset embeds Apache Superset dashboards.
Setup
Settings → Datasources → Superset. URL and credentials. Guest-token embedding must be enabled on the Superset side.
Why embed rather than rebuild
Superset is better at exploratory analytical dashboards than AccelerUp is, and the dashboards already exist. Rebuilding them here would produce two definitions of every metric, which reliably ends with two different numbers and an argument about which is right.
Dataset mapping
Superset datasets can be mapped to AccelerUp metrics, so a number defined once in Superset can appear in a KPI report without being redefined.
This is the main integration point and the reason to set it up: one definition, used in both places.
Alerting
Superset's own alerting is separate. For alerting on warehouse data, use SQL alerts — they share AccelerUp's routing, escalation, on-call, delivery retries and incident model, which Superset alerts do not.
Limits
Embedding depends on Superset's guest-token support and on its CORS configuration allowing the AccelerUp origin. If a dashboard renders blank, that is the first thing to check.
Where this behaviour lives: backend/internal/integration/superset.go, frontend/src/app/dwh/superset/. If the code and this page disagree, the code is right — please fix the page.
Part of Data warehouse — Querying the warehouse, and alerting on what the query returns.