Configure a lineage provider

Where: sidebar → Providers → Add Provider → Add Lineage. Use the service settings supplied for your installation.

Add Lineage configures endpoints, namespace, authentication, and enablement for the provider.

Enter the configuration#

Name the provider, enter its event endpoint and read endpoint as required, and choose its namespace and authentication type. Supply an API key only when the service uses one. Review enabled/disabled state and save.

The event-writing endpoint and graph-reading endpoint can serve different roles. Use the values for the actual service rather than copying an AI API endpoint into this form.

Verify the consumer#

Open the relevant resource's View Lineage action or sidebar Explorer. Inspect its nodes and edges after the workflow has produced lineage. Saving a provider does not generate historical events for work that never ran.

Explorer displays the resource dependency graph available in the current project.

If the graph is empty, check the project, permissions, root resource, completed runs, and provider availability. Distinguish configuration from a successful event submission and from a successfully read graph.

Changes to the provider can affect multiple consumers. Retain the intended namespace/job identity and verify a controlled event after editing an endpoint or credential. Ask the instance administrator to inspect service connectivity when the UI cannot retrieve lineage.