Beta feature. The reporting database is currently in beta. It's switched on per workspace by Azumuta, and the setup steps, available tables, and schema may still change while we finalize it. Contact your Customer Success Manager to join the beta.
What Is the Reporting Database?
The reporting database is an optional, read-only copy of your workspace's Azumuta data, kept in a standard PostgreSQL database with a flat, SQL-friendly structure.
It lets your data analysts and BI developers connect their own tools — such as Power BI, Tableau, Metabase, Looker, or any SQL client — directly to your Azumuta data, so they can build dashboards and run ad-hoc analysis without affecting the live system your teams use every day.
Why Use It?
The data that runs Azumuta day to day is optimized for operating your factory, not for analytics. The reporting database gives your analysts a stable, query-friendly copy that is:
- Read-only — you can query it freely; you can never change your operational data through it.
- Kept up to date automatically — Azumuta syncs your latest data into it on a schedule (by default, every 15 minutes).
- Selective — you choose which data to include, table by table.
- Isolated — each workspace has its own private area; your data is never mixed with another company's.
- Self-documenting — every table and column carries a built-in description, so the schema explains itself inside your SQL or BI tool.
Who Is It For?
This guide is aimed at data analysts and BI developers who are comfortable with SQL and connecting analytics tools to a database. Setting it up requires a workspace administrator.
How It Works, in a Nutshell
- A workspace administrator enables the reporting database and chooses which data to include.
- Azumuta creates a private area for your workspace and continuously syncs the selected data into it.
- You connect your SQL client or BI tool using the connection details Azumuta provides.
- You explore the schema and start running analytics queries.