Looker Performance Optimization - Episode 3

Key Concepts:

• Henry (LookML analyzer tool)
• Git integration (GitHub, GitLab)
• LookML project management
• Project backup and recovery
• Model and view file analysis
• Git connection status
• Pull request requirement
• Validation requirement

1. Introduction and Setup

• Mike DeAngelo, a developer relations engineer at Google, introduces the third part of the "Optimizing Looker Performance with Henry" series.
• He connects to a pre-configured Linux environment and navigates to the Henry directory.
• He activates a Python virtual environment using the command source bin/activate.

2. Running Henry to Analyze Projects

• The command henry analyze projects --section=sandbox is executed to analyze LookML projects within the "sandbox" section.
• The analysis process takes several minutes to complete.

3. Interpreting Henry's Output Data

• The output data from Henry provides insights into the status of LookML projects.
• The report includes the following columns:
  • Project Name: The name of the LookML project.
  • Model Files: The number of model files in the project.
  • View Files: The number of view files in the project.
  • Git Connection Status: Indicates the connection status to an external Git provider.
  • Pull Requests Required: Indicates whether pull requests are required for Git changes.
  • Validation Required: Indicates whether validation is required before committing Git changes.

4. Git Connection Status: The Most Important Field

• The Git Connection Status is highlighted as the most crucial field.
• An "OK" status signifies a fully connected project to an external Git provider (e.g., GitHub, GitLab).
• A project with an "OK" status has its LookML synced externally, allowing for easy recovery if the project is deleted from Looker.

5. Error Messages and Lack of Git Configuration

• Error messages in the Git Connection Status indicate improper Git configuration.
• This suggests that LookML updates might not have been performed recently, and the project may not be actively maintained.

6. "Bare Repo, No Test Required" Status

• A "Bare repo, no test required" status indicates that the project is not connected to an external Git provider.
• The LookML project is stored only on the Looker server.
• Deleting such a project makes recovery difficult.

7. Project Backup and Recovery Implications

• The report provides an overview of all projects, indicating which can be easily restored if removed and which require careful backup before removal.
• Projects with Git integration are easier to recover.

8. Next Steps: Model Analysis and Vacuuming

• The fourth installment will focus on analyzing and vacuuming models.
• This will provide more information about what is actively in use within the LookML projects.

9. Conclusion

• Henry provides valuable insights into the Git connection status of LookML projects.
• This information is crucial for determining the ease of project recovery and the need for backups before project removal.
• Proper Git integration is essential for LookML project management and disaster recovery.