Usage statistics

The usage statistics functionality is available starting from the Enterprise version 3.2.


Usage statistics is an optional feature which can be used to analyze usage using If enabled then report execution requests are stored in a special usage statistics account and usage statistics reports and dashboards can be created to analyze how reports are used by users.

On this page:


Usage statistics can be enabled in the eazybi.toml configuration file (or copy and uncomment settings from eazybi.toml.sample file):

enable = true


After saving the configuration file, please restart Enterprise server (Private server). A special (usage statistics) account will be created which will be available to system administrators. You can grant access to other users or user groups to this account.

A set of default reports and a dashboard of these reports will be created in this account. You can use these reports to see the overview of daily usage, see top executed reports and dashboards, reports with errors or slow reports.

Report execution data are stored in a separate database schema – eazybi_private_dwh_stats on MySQL, dwh_stats on PostgreSQL or MS SQL, the same user schema on Oracle. Report execution results are cached and the cache is cleared each 10 minutes – so you might see up to 10 minutes old data in your reports.

By default, 1-year history of usage statistics data is stored. Older usage statistics entries are deleted during the startup. You can change how long history is stored by adding an additional setting in eazybi.toml, for example:


keep_for = "3 months"


You can disable usage statistics by removing the enable line from the settings (or prefixing it with # which will comment this line). When usage statistics are disabled, then you can still view the collected historical usage statistics. If you do not need the history, then the (usage statistics) account can be deleted by the owner of this account.

Data model

Here is a list of measures and dimensions that are available in usage statistics reports.


Report ExecutionsA total number of first-time report executions when the report is opened (repeated executions are not counted when users change page selection or do drill actions).
Report Execution DurationTotal first-time report execution time in seconds. Use the Average Execution Duration calculated measure to get the average.
Report Execution ErrorsA total count of errors during the first-time report executions. Use the Report Execution Errors % calculated measure to see it as a percentage from total executions.
Active UsersUnique count of users who used reports according to the selection of other dimensions.
Active AccountsUnique count of accounts from which reports were used.
Active ReportsUnique count of reports which were used.
Active DashboardsUnique count of dashboards which were used.


Account account – name and ID.

Click on the dimension member and select Go to source to navigate to the Analyze tab of this account.

UserUser – display name and email.

Reports grouped by Account, Cube, Folder levels – name and ID.

Click on the dimension member and select Go to source to open the report.


Dashboards grouped by Account level – name and ID.

Click on the dimension member and select Go to source to open the dashboard.

Cube TypeBased on the data source – HansaWorld, JIRA or Custom.
Report TypeTable or a specific chart type.
Report LocationWhere a report was located – Analyze tab, Dashboard, Gadget Dashboard or Gadget Report.
TimeDate when a report was executed. The date is based on the server time zone.
HourHour of the day when a report was executed (e.g. 10 means that it was executed from 10:00 to 10:59). Hour is based on the server time zone.
Week DayThe day of the week when a report was executed.