Diagnose provider health, unresolved identity, disconnected assets, filters, and request bounds.
An empty graph does not prove that no dependency exists. Check provider delivery, identity resolution, source scope, filters, and response bounds.
curl --get "https://api.embrasure.ai/v1/lineage/providers/$PROVIDER_ID/gaps" \
--header "Authorization: Bearer $EMBRASURE_API_TOKEN" \
--data-urlencode "workspace_id=$WORKSPACE_ID" \
--data-urlencode "status=open" \
--data-urlencode "limit=50"Gap details include expected cadence, last receipt, backlog, normalizer version, and a bounded reason when available.
GET /v1/lineage/identity-issues lists ambiguous and unresolved assets. Filter by connector and status, then page with cursor.
Common fixes:
Traversal, impact, coverage, and export accept repeatable filters:
| Filter | Purpose |
|---|---|
environment | Limit results to mapped environments. |
connector_id | Limit results to one or more connectors. |
provider_type | Select native, OpenLineage, import, or static evidence. |
evidence_state | Select active, unresolved, ambiguous, retracted, or quarantined evidence. |
Filters narrow a read. They do not change connector scope or delete evidence.
GET /v1/lineage/disconnected-assets returns catalog objects without a resolved upstream edge, downstream edge, or either. Filter by workspace_id, environment, connector_id, provider_type, and reason, then page with cursor.
Reasons distinguish no evidence, unresolved evidence, filtered evidence, stale provider delivery, and intentionally isolated assets. This prevents an orphan report from treating every source table as broken.
Traversal responses state when depth, node, edge, column, or time limits truncate the result. Narrow the root, direction, environment, provider, or column before drawing a completeness conclusion.