Lineage for assets
For some asset types, you can see the lineage of each asset. Lineage is the history of the events performed on the asset in Watson Studio, Watson Knowledge Catalog, and Watson Machine Learning. A lineage event is an action that changes or copies the asset. For example, editing the asset description is a lineage event, but viewing the asset is not a lineage event.
To view lineage for an asset, click the asset name in a project or catalog and click the Lineage page. The lineage graph shows a timeline of events. Summary information about the asset’s lineage shows where asset was created, how many times it was added to projects or catalogs, what the last event for it was, and when the last event happened. Click an event to see its details. The first event for each asset is its creation.
You can see this type of information about each lineage event:
- Where: In which catalog or project the event occurred.
- Who: The name of the user who performed the action, unless the action was automated. Automated actions generate lineage events, but don’t show user names.
- What: A description of the action. Some events show details about the original and updated values.
- When: The date and time of the event.
Lineage also tracks relationships between assets. In the lineage graph, the creation of a new asset based on the original asset is shown as a branching event. For example, when you add an existing catalog asset to a project or publish an existing project asset to a catalog, you create a new asset that is a copy of the original asset. Double-click the branching event to expand and view the node for the related asset. Click the link for the related asset on the event details pane to go to that asset.
Watch this video to see how to track the lineage of a data asset in Watson Studio and Watson Knowledge Catalog.
Watch this video to see how to track the lineage of a Watson Machine Learning model in Watson Studio and Watson Knowledge Catalog.
Requirements and limitations
Lineage is not available with all Watson Studio and Watson Knowledge Catalog plans.
Lineage has the following limitations:
- Only assets that are created after lineage tracking began on 20 July, 2018, have lineage graphs.
- Lineage graphs are currently available only for Watson Machine Learning models and data assets.
- Lineage graphs do not appear in Microsoft Internet Explorer 11 browsers
Lineage events can describe actions that are applicable to all asset types or actions that are specific to an asset type:
- General lineage events
- Events specific to Watson Machine Learning models
- Events specific to data assets from files and connected data assets
General lineage events
You can see these general lineage events:
- Published to a catalog from a project
- Added to a project from a catalog
- Name updated
- Description updated
- Tags updated
- Classification updated
- Membership updated
- Privacy updated
- Owner updated
Events specific to Watson Machine Learning models
Lineage tracking is available for all Watson Machine Learning service plans, however, you won’t see events for actions that are not available with your plan.
In addition to general events, you can see these lineage events that are specific to models:
- Model created
- Model deployed
- Model re-evaluated
- Model retrained
- Set as active model
- Model deployment payload logged (Enterprise plan only)
- Deployment payload logging enabled (Enterprise plan only)
- Deployment payload logging disabled (Enterprise plan only)
A model asset shows this information in the Created from field, depending on how it was created:
- The name of the associated data asset
- The name of the associated connection asset
- The project name where it was created
Events specific to data assets from files and connected data assets
In addition to general events, you can see these lineage events that are specific to data assets from files and connected data assets:
- Added to project from a Data Refinery flow
- Added to a project from a file
- Added to a catalog from a file
- Imported to a catalog from Information Governance Catalog
- Added to a catalog by Information Governance Catalog synchronization
- Properties updated by Information Governance Catalog synchronization
- Name updated by Information Governance Catalog synchronization
- Description updated by Information Governance Catalog synchronization
- Schema updated by Information Governance Catalog synchronization
- Data classes updated
- Schema updated by a Data Refinery flow
- Profile created
- Profile updated
- Profile deleted
A data asset shows this information in the Created from field, depending on how it was created:
- The name of the Data Refinery flow that created it
- Its associated connection name
- The project name or catalog name where it was created or came from