Celiq
v0.12Open app
Docs/Building/Metrics Catalog

Metrics Catalog

A read-only, searchable directory of every metric (reveal) defined across your workspace's domains.

Building
In this section
Part of Celiq's semantic layer platform. Connect your warehouse, model your data once, query it everywhere.

Metrics Catalog

What is the Metrics Catalog

The Metrics Catalog is a read-only browser for every metric — internally called a reveal — defined in your workspace. The page header in code describes it as "Every metric in your workspace — searchable and filterable," and a comment calls it the "App Store for metrics."

Reveals are not stored in their own table. The backend (catalogService.listReveals) flattens the reveals: array out of each domain's YAML (domains.content) and enriches each one with:

  • Certification — looked up best-effort from a reveal_certifications table; defaults to not-certified if the table is absent.
  • Usage countsquery_count, mosaic_count, and last_queried_at, derived best-effort from query_logs and mosaic_tiles, cached in memory for one hour.

When to use it

  • To find an existing metric before building a new one (avoid duplicates).
  • To see which metrics are certified vs. ad-hoc.
  • To spot metric disagreements — the page cross-references /api/conflicts and flags reveals that appear in an open conflict.

How to use it

  1. Open the Catalog.
  2. Filter by domain using the pills across the top (domains are derived from the loaded reveals).
  3. Toggle Certified only to hide uncertified metrics. The empty state says: "No certified metrics yet. Certify metrics in Forge."
  4. Sort by Most used (default), Name (A–Z), or Recently updated.
  5. Search by metric name or description.

The Catalog has no create/edit controls. Metrics are authored in Forge and surfaced here.

Key concepts / fields

Each metric card (MetricCard) is backed by a reveal object with these fields (from catalogService):

FieldMeaning
id${domain_name}__${reveal_name}
namereveal label, falling back to its name
descriptionfrom the reveal YAML
domain{ id, name, slug }
nodeprimary node, if the reveal declares primary_node
certified / certified_by / certified_at / certification_notefrom reveal_certifications
query_count / mosaic_count / last_queried_atusage signal
statusreveal status, else domain status, else published
updated_atthe domain's updated_at

Note: the Catalog hides reveals that have no description, no usage, and no certification (treated as auto-generated stubs) — unless nothing passes that filter, in which case it shows everything.

📸 Screenshot: Metrics Catalog with domain pills, certified toggle, and metric cards
📸 Screenshot: a metric card flagged with a conflict / disagreement note
  • Forge — where metrics (reveals) are authored and certified
  • Discover — query the metrics you find in the Catalog
  • Mosaics — dashboards built from reveals
  • Contracts
Status: built (read-only list + filters + conflict flagging are implemented). The certification and conflict-detection workflows that feed it are referenced but not fully traced here — those before publishing.