Knowledge Drop

Track Downloads in System Activity (workaround)

Userlevel 1

Last tested: Nov 26, 2020

It's currently not possible to track download events in i__looker / System Activity. Be sure to give a +1 to the request:

Workaround: You'll need to piece together different explore results so it's admittedly not as straightforward as running one report.

The "event_attribute" explore in the system__activity model can report all downloads when the renderer is not invoked (i.e.: the format is not PDF or an image). The history_id attribute value can be related back to results in the internal "history" explore:





Next, the "history" explore can provide explore, model, fields, connection, user, and time for a download event. Relating values from this explore to (1) should get you everything that you need regarding the source of the content:




Finally, the "event_attribute" explore can also report all the times during which the renderer is invoked, and indicate if a PDF or PNG / etc. was pulled:




This content is subject to limited support.                



2 replies

Does this workaround still work? I can’t seem to identify a join relationship between “event_attribute” and “history” using <history_id>. (Lots of NULLs)



Userlevel 7

It’s really disappointing that the system activity model can not be extended to allow people to cope for their specific use cases.

This specific scenario should perhaps already be possible with what is prebuilt but it’s still more than valid the many questions people want and need to answer and they cannot because the ability to make use of Lookers modelling ability is restricted. The workaround (ETL it and then re-model it from scratch) is also unreasonable!