Metadata / AI Governance / Analytics

Google makes LookML metric definitions and lineage generally available in Knowledge Catalog

Looker Core on Google Cloud now indexes models, joins, metric formulas and dashboard lineage into Knowledge Catalog by default, so Gemini Enterprise and custom agents can ground SQL in certified business logic.

Product launchGlobalNotableAvailableOfficial source
GA: LookML semantics and lineage now indexed in Google's Knowledge Catalog by default

Google Cloud has announced the general availability of LookML indexing in Knowledge Catalog for Looker Core on Google Cloud. LookML models, Explores, views, field definitions, join conditions, mandatory filters and dashboards are synchronised into the catalog. According to Google, this lets Gemini Enterprise and custom agents use exact metric formulas rather than inventing SQL.

The documentation says synchronisation is on by default and needs no configuration. Updates pushed to production LookML are reflected through a live sync. Lineage runs from BigQuery tables to individual dashboard tiles, supporting impact analysis and upstream audit. Storing Looker technical metadata carries no charge, although standard pricing applies to API calls and business metadata enrichment.

Administrators can opt out. If they do, metadata already in the catalog remains there but is no longer updated. Gemini Enterprise queries the catalog using end-user credentials, so users see only the assets their IAM roles permit.

Editor’s note: Both sources are Google’s own announcement and product documentation; the claims have not been independently verified.

Why it matters

Metric definitions, filters and ownership become catalog metadata that AI agents treat as authoritative, so certification and stewardship of LookML models now directly affect the quality of agent answers. Teams should decide which models count as certified before agents start consuming them. They should also confirm that access filters and column-level tags are set correctly, because the integration is on by default. Note that an opted-out instance leaves stale metadata in the catalog, which may need cleaning up.

Status: Available. enabled by default on Looker Core on Google Cloud instances

Sources

  1. Unifying enterprise context and semantics: LookML in Knowledge Catalog is now GA — Google Cloud BlogPrimary source
  2. Manage Looker (Google Cloud core) metadata in Knowledge Catalog — Google Cloud documentationPrimary source

Was this useful?

Prepared with AI assistance and reviewed by the editor before publication. Spotted an error? Tell us — see our editorial policy and methodology.

Governance areas

Who should care

  • CDO
  • Data stewards
  • AI governance lead
  • BI and analytics leads

Related

Latest

All news

Contact the editor

Tips, corrections, questions?

Write to The Steward, the editor of Data Governance Signal. Every message is read.

editor@datagovernancesignal.com