Skip to main content

Atlassian Audit Logs connector reference

Beta

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.

Reference information for the managed Atlassian Audit Logs connector, including the supported source table, the audit_logs destination schema, and connector options.

Supported source tables

The Atlassian Audit Logs connector supports the following source table, under the default source schema:

Source table

Primary key

Description

Sync mode

Cursor field

audit_logs

id

Audit log events for your Atlassian organization, such as user, security, and configuration changes.

Incremental

time

Source table

Primary key

Description

Sync mode

Cursor field

audit_logs

id

Audit log events for your Atlassian organization, such as user, security, and configuration changes.

Incremental

time

Connector options

The Atlassian Audit Logs connector supports the following pipeline-level configuration option. Set it in the source_configurations block of your pipeline definition. See Examples for usage.

Option

Type

Scope

Required

Applies to

Description

start_datetime

String

Pipeline

No

audit_logs

The start of the initial backfill window, as an ISO 8601 timestamp (for example, 2026-01-01T00:00:00Z). When omitted, the first sync starts 180 days before the pipeline runs.

Option

Type

Scope

Required

Applies to

Description

start_datetime

String

Pipeline

No

audit_logs

The start of the initial backfill window, as an ISO 8601 timestamp (for example, 2026-01-01T00:00:00Z). When omitted, the first sync starts 180 days before the pipeline runs.

Destination table schemas

audit_logs

Primary key: id Cursor field: time

Field

Data type

id

STRING

type

STRING

time

TIMESTAMP

action

STRING

actor

STRUCT<id: STRING, name: STRING, email: STRING, picture: STRING, links: STRUCT<self: STRING, alt: STRING>>

context

VARIANT

container

VARIANT

location

STRUCT<ip: STRING, geo: STRING, countryName: STRING, regionName: STRING, city: STRING>

message

STRUCT<content: STRING, format: STRING>

links

STRUCT<self: STRING, alt: STRING>

relations

VARIANT

Field

Data type

id

STRING

type

STRING

time

TIMESTAMP

action

STRING

actor

STRUCT<id: STRING, name: STRING, email: STRING, picture: STRING, links: STRUCT<self: STRING, alt: STRING>>

context

VARIANT

container

VARIANT

location

STRUCT<ip: STRING, geo: STRING, countryName: STRING, regionName: STRING, city: STRING>

message

STRUCT<content: STRING, format: STRING>

links

STRUCT<self: STRING, alt: STRING>

relations

VARIANT

note

This table does not support SCD type 2 because it has VARIANT columns.

Required Atlassian account permissions

Permission

Required for

Organization admin

Baseline access

Permission

Required for

Organization admin

Baseline access