Extension not interacting in dashboard.

[justin-fell-acn]

Hello! This project is awesome, and I really appreciate you sharing your path to incorporating gemini in looker. I am having an issue where I cannot interact with the extension when I have it in my dashboard. Is there any sort of additional setup I need to do with Gemini + Vertex AI in GCP? Feel like I'm so close to having this working but stuck here, let me know if you had this issue! Thanks!

[alexanderwhatley]

Exact same issue here.

[LukaFontanilla]

If the Generate button remains greyed out, that means the Websocket Service (used for the Looker to Vertex AI connection ) is not able to connect.

For developing locally, please make sure the websocket server is running first then open up the browser console to see what errors are displayed.

For a production deployment, please ensure the websocket server was successfully deployed to Cloud Run and is open to public traffic.

It's likely a configuration somewhere on the websocket server, given that the Extension Tile loads. On the backend deployment there should be 2 areas to customize:

• looker.ini: for Looker API configuration. ini file header should be the host name of your instance (ie. mycompany.cloud.looker.com -> header should be mycompany).
• terraform/variables.tf: there are example defaults configured here, these should be replaced with those for your environment prior to deploying the backend.

[alexanderwhatley]

Hi @LukaFontanilla I'm not sure that actually solves the issue at hand. Looking at the code, it appears that the "Generate" button is disabled if the socket connection is not set -

dashboard-summarization/src/DashboardSummarization.tsx

Line 279 in 3d6defc

<button className='button' style={{lineHeight:'20px', padding:'6px 16px'}} disabled={loading || !socket.connected} onClick={() => {

.

Looking at the code that sets the socket connection, in production it is set to be the "WEBSOCKET_SERVICE" environment variable:

dashboard-summarization/src/socket.ts

Line 29 in 3d6defc

const URL = process.env.NODE_ENV === 'production' ? process.env.WEBSOCKET_SERVICE!

. However, this is an optional environment variable according to the README, and the README never calls out the purpose of this environment variable.

Can you please let me know if I'm missing something?

[LukaFontanilla]

@alexanderwhatley the WEBSOCKET_SERVICE env variable is required. The optional variables are those for the export options like Slack and Gchat (we can make this more clear).

On the frontend side there are two places where the WEBSOCKET_SERVICE url needs to be set.

• in the .env file in the root directory (as mentioned above)
• in the LookML Project Manifest file, replacing the YOUR_CLOUD_RUN_URL with the URL for the deployed Cloud Run service. This is because the extension requires any external API url called in the Frontend to be allowlisted.

[alexanderwhatley]

@LukaFontanilla understood, but it is never specified that it is required, nor is it specified what it is. Can you make those changes in the README?

[hitesh-goel]

I am facing the same issue, while in my case i am able to click Generate button but it's stuck on this next page. For more context our looker instance is self hosted, so it's mycompany.looker.com instead of mycompany.cloud.looker.com as mentioned in document. is this somehow related? Thanks