Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Atlassian Audit Logs from the Previews page. See Manage Azure Databricks previews.
The managed Atlassian Audit Logs connector ingests only the audit_logs table, and Atlassian retains audit log events for up to 180 days, which limits how far back the connector can backfill.
General software as a service (SaaS) connector limitations
The limitations in this section apply to all SaaS connectors in Lakeflow Connect.
- When you run a scheduled pipeline, alerts don't trigger immediately. Instead, they trigger when the next update runs.
- When a source table is deleted, the destination table is not automatically deleted. You must delete the destination table manually. This behavior is not consistent with Spark Declarative Pipelines on Lakeflow behavior.
- During source maintenance periods, Databricks might not be able to access your data.
- If a source table name conflicts with an existing destination table name, the pipeline update fails.
- Multi-destination pipeline support is API-only.
- You can optionally rename a table that you ingest. If you rename a table in your pipeline, it becomes an API-only pipeline, and you can no longer edit the pipeline in the UI.
- If you select a column after a pipeline has already started, the connector does not automatically backfill data for the new column. To ingest historical data, manually run a full refresh on the table.
- Databricks can't ingest two or more tables with the same name in the same pipeline, even if they come from different source schemas.
- The source system assumes that the cursor columns are monotonically increasing.
- The connector ingests raw data without transformations. Use downstream Spark Declarative Pipelines on Lakeflow pipelines for transformations.
Connector-specific limitations
The limitations in this section apply to the Atlassian Audit Logs connector.
- The connector ingests a single table,
audit_logs. It doesn't ingest other Atlassian Admin API resources, such as users, groups, domains, or policies. - Atlassian retains organization audit log events for up to 180 days. The connector can't ingest events older than this retention window.