​
Description

The Explore Assistant allows a user to generate a Looker Explore Query via natural language outputted into a visualization. As opposed to writing the raw SQL itself, the LLM is optimized to translate a text input into a Looker explore query. This is important as the LLM does what it’s great at, generative content, and Looker powers it with all the underlying data context, metadata and nuances that come with business data and analytics. Additionally, the extension provides:
  • Question History (this is stored in the browser’s localstorage)
  • Categorized Prompts (these can be customized by the use cases of your organization)
  • Cached Explore URL’s when clicking from History
  • Structured Logging with Input & Output Token Counts (enables a workflow of log sink to BQ for cost estimation & tracking)
  • Flexible Deployment Options
  • Multi-turn
  • Insight Summarization

​
Technologies Used

​
Frontend

​
Looker

​
Backend API

​
Setup

Getting started involves: The local cloud function backend and example generation require some python packages. It is recommended to create a python virtual environment and install the dependencies: 
python3 -m venv .venv
source .venv/bin/activate 
pip3 install -r ./explore-assistant-examples/requirements.txt
pip3 install -r ./explore-assistant-cloud-function/requirements.txt

​
Recommendations for fine tuning the model

This app uses a one shot prompt technique for fine tuning a model, meaning that all the metadata for the model is contained in the prompt. It’s a good technique for a small dataset, but for a larger dataset, you may want to use a more traditional fine tuning approach. This is a simple implementation, but you can also use a more sophisticated approach that involves generating embeddings for explore metadata and leveraging a vector database for indexing. Any jsonl file you see in this repo is used to train the llm with representative Looker Explore Query examples. These examples are used to help the understand how to create different variations of Looker Explore Queries to account for requests that might result in pivots, relative date filters, includes string syntax, etc. For convenience and customization we recommend using Looker System Activity, filtering queries for the model and explore you plan on using the assistant with, and then using the top 20-30 queries as your example input output string with their expanded url syntax.