Henry - A Command Line Tool for Looker Instance Cleanup

(Joseph Axisa) #1

As a Looker model grows in size and sophistication, we may have an ever-increasing number of Explores, Views and Fields. It's important to ensure we only expose those that are useful to our end users.

Henry is a tool I created to help Looker admins and developers identify which aspects of the model are not being used, or “Model Bloat”, that can be safely removed.

More information about setting it up and usage can be found at https://github.com/looker-open-source/henry/wiki.

Please note that this tool is open source and is not supported by Looker’s normal support channels. However, any issues encountered while using the tool are encouraged to be filed here: https://github.com/looker-open-source/henry/issues as it will help contributors enhance it further.


Possible to hide joins?
(Ian) #2

Hi @jax we have only just got around to looking at this tool after speaking with @Katie_Hindson at a London Looker meetup. We both are trying to automate the cleanup process. I have documented how it would work to automate cleanup for content, users, spaces, connections and explores but I was wondering if you could see a way to hide/remove models, projects, pdts & datagroups.
Also what do you see as the future/next steps of this tool. Would removing the manual next steps after analysis using Henry and automating these fit with your vision of this tool?



(Nicholas Wong) #3

Thanks Joseph! Henry will be a great tool for developers to clean up their codes. I have had face challenges on deciding which block of codes are used and which codes can be deleted. I’m really excited to try this out! :smiley:

1 Like

(Joseph Axisa) #4

Hey @iant! Unfortunately I missed that event but I will do my best to be at the next one.

I did some research to answer your questions however I ended up with more questions myself due to certain behaviour I encountered. I will reach out to you directly via email.

With regards to future/next steps of this tool, having the option to automatically remove/hide fields is not on the radar since the results do require some analysis by the user before deciding whether to remove a field or not. Some features that I am currently working on include being able to count indirect usage of fields, some more actionable content stats and adding the ability to generate some form of report from the tool.


(Joseph Axisa) #5

Happy to hear that Nicholas. I’m interested to know how you get on with this. Please feel free to leave feedback here, in the repo or sent directly to me once you’ve had a chance to try this out.


(Ian) #6

When I say automatically take actions I meant that actions could be scripted rather than done by the user in the UI.
As I said previously, some actions the user would want to complete are possible using the API, the rest I don’t think are :cry:

1 Like