When the cycle of planning starts it is important to track all inputs. One reason is for monitoring purposes [Who did when what and why] and the second is to keep the log of how data looked before that step. For that purpose, we will use Audit functionality.
This functionality can be found in the Administration tab:
By default, an audit is not started until the user enables it in Settings Panel. Auditing can be done for 1,7,30 or 365 days. Have in mind that a larger auditing period is selected, the file on your server will take more memory. Once you select the cube which should be monitored, add some value inside. In our case, we will add 400 Units for Handlebars inside Orders Cube which we previously enabled in Audit.
After hitting that splash functionality new value is visible in the Audit section.
Now, you can check why the values are appearing in the report since everybody claims it was not their fault π
Sometimes, we would like to use this table and create a report from it. It could be useful for End Users which have only a Viewer license. All Audit data is stored in Audit.SQLite database which could be found inside OLAP/data/[DatabaseName in this case Biker]/audit.SQLite. When we know that, we can create ETL which will extract that data.
………………………………………………………………………………………………………………………………………………………………
This example is from Jedox on-premise. If your on-premise application doesn’t allow extract from this SQLite location, check the following page for the solution. In case your solution is on the cloud, the SQLite database will probably be stored here
/user_data/live/Data//audit.sqlite
Of course now when you have data extracted in ETL you can create your own monitoring cubes and fill them with data.
ETL project can be found here.