Skip to main content
Preview If your team already has a semantic layer, such as Snowflake semantic views, Databricks metric views, or a dbt semantic model, you don’t have to replace it. Keep it for the people and tools that use it, and use it as a source for Metric Studio.

Same parts, organized differently

A semantic layer and Metric Studio hold the same parts: what tables mean, how they join, metrics, and the dimensions a metric can be split by. Most semantic layers organize them by table or by view. Metric Studio organizes them by metric: its formula, filters, joins, dimensions and trusted SQL are stored together, and tables are referenced from it. That matters once agents answer questions, because questions start with a metric, not a view: Organizing by metric has costs too: questions no metric covers fall back to exploration, and without review, metrics sprawl into near-duplicates. For the full case, benchmark results, and how each tool compares, see Why a metric, and not a view and Semantic layers compared in the analytics agents playbook.

Bring definitions you already have

The Analytics plugin reads a declared semantic model as a source, such as a Snowflake semantic view or dbt model files. Each declared measure becomes a candidate metric, and query history fills in what the model leaves out. You review every metric before it’s written, and nothing is written back to your semantic layer. Metric Studio doesn’t watch your semantic layer for changes. When a model changes, run the plugin on it again: it reuses the metrics already in the workspace instead of making duplicates.

Metric Studio and the catalog glossary

A glossary term in the Agentic Data Catalog explains a business term to people and usually has no SQL. A Metric Studio metric gives agents the calculation. Metric Studio doesn’t read the glossary: to turn a term into a metric, give its definition to your agent as A business question in Build your first metrics, and review the calculation it proposes.