Acceldata 26.4.0 introduces targeted enhancements to the SnapLogic pipeline integration, addressing two persistent gaps: lineage visibility for Snowflake assets and support for nested pipeline relationships. For teams running complex integration workflows through SnapLogic, these updates deliver a more complete and accurate picture of how data moves across their stack.
The Challenge with SnapLogic Observability
SnapLogic pipelines frequently interact with external systems and are composed of nested pipelines that call one another at runtime. Capturing accurate lineage across these patterns has historically been constrained by SnapLogic’s native APIs.
Specifically, the lineage API provided by SnapLogic returns stale data for pipeline runs — making it unreliable as the sole source of lineage information. And because SnapLogic pipelines can trigger other pipelines, the lack of inter-pipeline linkage has left teams with a fragmented view that stops at the boundary of each individual pipeline rather than following the full execution chain.
Key gap: Without cross-pipeline visibility, teams lose the ability to trace data from source to destination when workflows span multiple nested SnapLogic pipelines.
What’s New in 26.4.0
Snowflake Asset Lineage for SnapLogic Pipelines
Acceldata now supports lineage extraction for Snowflake assets used within SnapLogic pipelines. Because SnapLogic’s native lineage API does not reliably surface this data, custom extractors have been built against SnapLogic’s native API to retrieve accurate asset-level information directly.
This gives teams visibility into which Snowflake tables and views are read from or written to as part of a SnapLogic pipeline execution — surfacing upstream and downstream dependencies that were previously invisible.
- Lineage is extracted for Snowflake assets connected to SnapLogic pipeline runs
- Custom extractors bypass the stale lineage API, pulling data from SnapLogic’s native API instead
- Upstream and downstream Snowflake asset dependencies are now visible within the pipeline view
Note: Snowflake is the first asset type supported via this extraction approach, prioritized based on usage patterns observed with AstraZeneca. Additional asset types may follow in future releases.
Inter-Pipeline Linkage for Nested Pipelines
SnapLogic uses a construct called Pipeline Execute to chain pipelines together — a parent pipeline can trigger one or more child pipelines as part of its execution. Acceldata now tracks and surfaces these pipeline-to-pipeline relationships, making the full execution chain visible in the UI.
When viewing a parent pipeline, any linked child pipelines are now shown with their relationship clearly represented. This linkage supports any level of nesting — so multi-hop pipeline chains are fully traversable rather than appearing as isolated, disconnected runs.
- Parent-to-child pipeline relationships are tracked and displayed in Acceldata
- Supports any depth of nesting in SnapLogic pipeline chains
- Enables end-to-end lineage tracing across interconnected SnapLogic workflows
One configuration requirement: the hostname used in the SnapLogic integration setup must match the hostname used when crawling and onboarding the data source. This consistency is what allows Acceldata to correctly stitch assets across pipelines.
What This Means for Teams
Together, these two enhancements close the most significant observability gaps for SnapLogic workloads:
- Teams can now trace data flowing through Snowflake from within SnapLogic pipelines, without manual investigation
- Impact analysis across nested pipeline chains becomes tractable — a change in a child pipeline can be traced back to its parent and the broader execution context
- Debugging integration failures is faster, with lineage context available directly in the pipeline view
- Observability coverage for SnapLogic workloads is now more consistent with what Acceldata provides for other supported pipeline integrations
Available Now
SnapLogic lineage enhancements are available as part of the Acceldata 26.4.0 release. No additional configuration is required beyond ensuring hostname consistency between the SnapLogic integration and data source onboarding. Reach out to your Acceldata Customer Success contact or visit the documentation portal for setup details.
.webp)
.webp)
