BETA: The reporting database is currently in beta and may still evolve. It is available by opt-in only. To join the beta or ask questions, contact support@azumuta.com.
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.
Connect your BI tools or SQL client to analyze Azumuta data without affecting the live system.
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).
- Complete: once enabled, it covers all of your workspace’s reportable data. There’s no per-table selection to manage.
- 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 for the workspace.
- Azumuta creates a private area for your workspace and continuously syncs all reportable 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.