Explore VegaGraph in the dashboard
Find a resource, inspect Entity 360, follow lineage and compare environment context.
Start with a resource already present in your workspace graph. This walkthrough follows it from search to identity, metadata and dependencies.
If the graph is empty, an authorized producer must first write entities and relationships through the API or a supported integration. Use the API getting-started guide to create a small example graph.
Select scope
Choose the organization and workspace that own the metadata. Confirm your access before interpreting an empty list. See organizations and workspaces.
Open Overview
Open VegaGraph → Overview to see the available graph at a high level. Counts and summaries reflect your permissions.
Search for a resource
Open Explore and enter a known name or fully qualified identifier. Narrow results with the available entity type, label or context filters, then select a result.
Inspect Entity 360
Confirm the resource's identity and qualified name. Review its aspects, version history, aliases, labels, fields, hierarchy and related edges where present. The Entity 360 guide explains what each part tells you.
Follow lineage
Open Lineage for the resource. Choose upstream to investigate inputs or downstream to investigate consumers. Start with a shallow depth and a specific relationship filter.
Entity lineage and field lineage can differ. Column-level dependencies require field references and their edges to have been ingested.
Compare contexts
When contexts are configured, compare the default context with another environment or child context. Check which facts are direct, inherited or canonical. Changing the selected context can change the resolved facts without changing the resource's core identity.
Interpret the result
Hierarchy describes structural containment. Lineage follows typed dependencies. Context selects the environment or perspective through which facts are resolved. Keep these three controls distinct when investigating a resource.
An impact view reflects the relationships and evidence currently in the graph. It does not prove that every external dependency has been ingested.
Empty or incomplete results
Check organization/workspace, selected context, filters, search and entity permissions, and whether the needed entities, fields and edges exist. Newly written metadata may also need an updated search document.
Continue with search and product views, relationships and traversal or troubleshooting.