Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
matthewharrison
Contributor III
Contributor III

Qlik Audit API for Sheet Usage

Our team was happy to see recently that Qlik exposed a new Audit API event to reflect user views of individual sheets.  This theoretically gives us the ability track the usage across all our reports to understand user adoption of our BI offerings.  Despite this, we are encountering several problems operationalizing this Audit API event to a useful level.  Our end goal is to have data in a form that lists how many times a sheet was viewed over a period of time along with related dimensions such as app, space, user name, and any other insightful info available. 

We experimented briefly with adapting the existing community monitoring apps to try and add this Audit event but have little experience with the level of scripting required.  The ideal solution would be a Qlik app like these monitoring apps that would allow us to pull data through a REST connection, store it in QVD form and then aggregate sheet usage events by user/app/timeframe/etc.  

We are also able to reach this info through the Qlik-CLI, but are apprehensive to start building infrastructure to automate and store this data without exploring other options.

Has anyone experimented with possible tools/Qlik apps/automations to leverage this new API event?  Does the Qlik product team have plans to release any native functionality to make this data more accessible?

Any input or suggestions are appreciated!

 

 

Labels (2)
11 Replies
Daniel_Pilla
Employee
Employee

@matthewharrison - Yes, I realize it is a glaring gap, but sheet names and types are not available RESTfully at this time. It is on the roadmap and is under development and will be added immediately upon completion. I don't have a timeline for that, however. It comes with a much larger initiative to make engine-only data available RESTfully.

Cheers!

matthewharrison
Contributor III
Contributor III
Author

Thanks!  That makes sense.  We will keep an eye out for any word on that enhancement!