What does Atlan crawl from Alteryx? Private preview
This document outlines the Alteryx metadata that Atlan crawls and maps as part of its cataloging process. Atlan supports two ingestion modes with varying property coverage.
Once Alteryx is integrated with Atlan, connector-specific filters can be used for efficient asset discovery.
Supported filters
| Filter Type | Description |
|---|---|
| Status filter | Filters workflows by their last run status. |
| Duration filter | Filters workflows by their last run duration. |
Asset mapping
Alteryx workflows are represented in Atlan using the AlteryxWorkflow asset type. The following table shows how Alteryx properties are mapped to Atlan properties:
| Alteryx Source Property | Mapped Atlan Property |
|---|---|
eventTime | alteryxRunStartTime |
eventTime | alteryxRunEndTime |
eventType | alteryxRunOpenLineageState |
runid | alteryxRunID |
job.owners | sourceOwner |
workflowID | alteryxWorkflowID |
run.errorMessage | alteryxWorkflowError |
- Multiple
eventTimefields are mapped to bothRun Start TimeandRun End Time, depending on context. - Workflow run metadata includes operational details like error messages and lineage states, which are essential for observability and debugging.