Query audit
Who ran what, against which connection, and what it returned.
Data Warehouse → Query Audit records every query AccelerUp runs against a warehouse.
What is recorded
| The query | Full text |
| Who | The user, or the rule/schedule that owns it |
| When | |
| Connection | |
| Duration | |
| Rows | |
| Outcome | Success, error, timeout |
What it is for
Compliance. Access to business data is auditable, which is usually a requirement wherever the data is regulated.
Debugging. When a rule behaves unexpectedly, the audit shows the exact query that ran and what it returned.
Cost. Pairs with the cost monitor to attribute load.
Automated queries too
Alerts, dashboards, scheduled queries and reports are all recorded, alongside the rule or dashboard that owns them. "Which alert is hammering this table" has an answer.
Retention
Audit records fall under the organisation's retention policy. Where a compliance regime requires a specific period, set it explicitly rather than relying on the default.
Related
- Audit log — actions in AccelerUp itself
Where this behaviour lives: frontend/src/app/dwh/audit/. 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.