Atlassian Audit Logs connector FAQ
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 Databricks previews.
Common questions about the managed Atlassian Audit Logs ingestion connector: required Atlassian plans, supported tables, backfill depth (up to 180 days), and authentication methods. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which Atlassian plans does the connector require?
The connector requires an Atlassian Guard Standard, Atlassian Guard Premium, or Cloud Enterprise subscription. Atlassian doesn't populate the organization audit log without one of these plans.
Which tables does the connector support?
The connector supports the audit_logs table only. For the destination schema, see Destination table schemas.
How far back can the connector ingest data?
For the first sync, the connector ingests events from the previous 180 days, unless you set the start_datetime connector option to a different value. Each later sync ingests events modified after the last run. Atlassian retains organization audit log events for up to 180 days, so the connector can't ingest events older than that.
Which authentication methods does the connector support?
The connector supports a Atlassian organization API key only. OAuth U2M, OAuth M2M, and basic authentication with a username and password aren't supported.