Seeing this supported by more users, I thought to share the workaround that we found for us.
Using an SQL dashboard (holistics 2.0), you just take any of the tiles and hardcode an insert statement right before the actual business logic. This is how it could look like
INSERT INTO dashboard_access_logs VALUES (NOW(),âDashboard XYZâ);
select from ; â whatever you would normally do here
As you know which dashboard it is, you hardcode the title parameter to contain the dashboard name. The timestamp parameter will allow you to analyze later. Do not forget to click the radio button ânon-select queryâ as otherwise holistics will complain that this is not a SELECT statement.
For also being able to track a dashboard 3.0, we created a database function which does the same insert statement but additionally returns the timestamp. (Actually we could use the same approach for dashboards 2.0, too, now that I am thinking about it ;)) Additionally, we created one individual data model per dashboard that we want to track. The data model basically just does this:
SELECT insert_dashboard_tracking(âDashboard XYZâ) AS current_time_stamp
Now you will need a separate tile on your dashboard XYZ showing âcurrent_time_stampâ from the corresponding data model XYZ. You need this step since if the data model is not really used, it will not trigger the insert.
Having a table with access timestamps and dashboard name in your DWH, you now can build your own dashboard visualizing access over time grouped by dashboard name, for instance.
Hope this helps 