This documentation page describes the latest Private eazyBI version 4.6.
Usage statistics is an optional eazyBI feature which can be used to analyze eazyBI usage using eazyBI. If enabled then eazyBI report execution requests and source data imports are stored in a special usage statistics eazyBI account and usage statistics reports and dashboards can be created to analyze eazyBI usage.
Usage statistics can be enabled in the
eazybi.toml configuration file (or copy and uncomment settings from the
After saving the configuration file, please restart Private eazyBI. A special (usage statistics) eazyBI account will be created which will be available to system administrators. You can grant access to other Jira users or user groups to this eazyBI 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 eazyBI database schema –
eazybi_private_dwh_stats on MySQL,
dwh_stats on PostgreSQL or MS SQL, the same eazyBI 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 eazyBI startup. You can change how long history is stored by adding an additional setting in
eazybi.toml, for example:
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.
Here is a list of measures and dimensions that are available in usage statistics reports.
|Report Executions||A 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 Duration||Total first-time report execution time in seconds. Use the Average Execution Duration calculated measure to get the average.|
|Report Execution Errors||A 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 Users||Unique count of users who used reports according to the selection of other dimensions.|
|Active Accounts||Unique count of eazyBI accounts from which reports were used.|
|Active Reports||Unique count of reports which were used.|
Unique count of dashboards which reports were used.
Import Count NEW
|Count of source data import runs.|
Import Duration NEW
|Duration of imports. Use the Average Import Duration calculated measure to get the average.|
Import Errors NEW
|A total count of errors during the first-time import run. Use the Import Errors % calculated measure to see it as a percentage from total imports.|
Import Canceled NEW
|Count of manually canceled imports.|
Step Import Count NEW
|Count of steps executed during import.|
Step Import Duration NEW
|Duration of import of each step. Use the Average Step Import Duration calculated measure to get the average.|
Units Imported NEW
|Count of Source units imported with each import. Use the Average Step Import Duration calculated measure to get the average.|
Units Import Duration NEW
|Duration of import of each Source unit. Use the Units Imported Per Second calculated measure to get an average of how many unites are imported per second.|
eazyBI account – name and ID.
Click on the dimension member and select Go to source to navigate to the Analyze tab of this account.
|Time||Date of activity logged in usage statistics.|
|Hour||Hour of the day of the activity logged in usage statistics. Hour is based on the Jira server time zone.|
|Week Day||The day of the week of the activity logged in usage statistics.|
|Dimensions for report executions analysis:|
|User||User – 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 Type||Based on the data source – Jira or Custom.|
|Report Type||Table or a specific chart type.|
|Report Location||Where a report was located – Analyze tab, Dashboard, Gadget Dashboard or Gadget Report.|
|Dimensions for source data import analysis:|
Import type NEW
|Full or Incremental import of source data. Incremental import could include Full data import of some import steps.|
Individual source application or source file from which the import was done.
Click on the dimension member and select Go to source to open the Source Data tab for the corresponding account.
Source type NEW
Source type, for example, Jira, SQL, REST API, etc. Some source types could be expanded to Source Steps representing a step of an import (for example, Project import, Issue import steps in Jira import).
Source Unit NEW
|Countable source units in import. For example, Issues, Projects, Objects, Rows, etc.|