Entity 360
Read a resource's identity, versioned facts, hierarchy, fields and dependencies in context.
Entity 360 brings a resource's identity, current metadata and relationships into one detail view. Open it from a search result, then confirm the resource and context before following its dependencies.
Read the resource
| Area | What to inspect |
|---|---|
| Identity | Entity type, fully qualified name, display fields, aliases, organization and workspace. |
| Aspects | Current facts such as ownership, description, quality or runtime metadata. |
| Versions | Earlier assertions and evidence behind metadata changes. |
| Labels | Managed classifications used for discovery and governance. |
| Fields | Addressable nested fields, such as columns, that can participate in field lineage. |
| Hierarchy | Parent/child containment and the resource's structural path. |
| Relationships | Typed edges to resources or fields, interpreted with their direction. |
| Context | The selected lens and whether facts are canonical, direct or inherited. |
An alias helps find a resource but does not replace its canonical identity. A missing aspect can mean the type does not bind it, it has not been ingested, or the current identity cannot view it.
Investigate a change
- Confirm the entity's qualified name and selected context.
- Review the current aspect and compare its version history where available.
- Check provenance to identify the source and observation behind the assertion.
- Follow upstream relationships for inputs or downstream relationships for consumers.
- Compare another context when the change appears environment-specific.
Hierarchy answers where a resource belongs. Typed relationships answer how it connects to other resources. Use lineage and traversal for dependency questions.
API and larger results
GET /entities/{entity_id}/360The response combines bounded identity, aspect, field, edge and context information. Use dedicated list and traversal endpoints for larger investigations. Specialized table, service, repository, KPI and environment views add resource-specific projections over the same graph.
See entities and aspects for write contracts, search and product views for discovery, and contexts and lineage for resolution rules.