This workflow uses the VegaLake dashboard and an existing workspace graph. If the graph is empty, an authorized producer must ingest entities and relationships through the public API or another supported integration first; ingestion is outside VegaGraph itself.
Choose the organization and workspace that own the metadata. Search, type catalogs, labels, contexts, and entities are tenant-scoped, so an incorrect selection can produce a valid empty state.
Open Explore, enter a known resource name or qualified identifier, and apply available type, label, or context filters. Select a result to open its details.
Review the entity’s identity and qualified name, aliases, aspects, aspect versions, labels, hierarchy, related edges, field references, and search document where present.
Open Lineage from the selected resource. Choose upstream or downstream direction, appropriate depth, and relationship filters. Field-level lineage may differ from entity-level lineage.
When contexts are configured, compare the default context with another environment or child context. Context overlays can change the resolved facts without changing the entity’s core identity.
Confirm scope, context, filters, search permission, entity permission, and whether the necessary edges or field references were ingested. Continue with Explore and search or Lineage.