Anysphere Audit Logs connector

Important

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Anysphere Audit Logs from the Previews page. See Manage Azure Databricks previews.

The managed Anysphere Audit Logs connector in Lakeflow Connect allows you to ingest audit logs from Anysphere (Cursor) into Azure Databricks.

Feature availability

Feature	Availability
UI-based pipeline authoring	Supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported Supported for the audit_logs table using the timestamp cursor field.
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported
SCD type 2	Not supported Audit log event data does not support SCD type 2.
API-based column selection and deselection	Supported
API-based row filtering	Not supported
Automated schema evolution: New and deleted columns	Supported
Automated schema evolution: Data type changes	Not supported
Automated schema evolution: Column renames	Not supported Requires a full refresh.
Automated schema evolution: New tables	Supported If you ingest the entire schema.

Authentication methods

Authentication method	Availability
OAuth U2M	Not supported
OAuth M2M	Not supported
Basic authentication (username/password)	Not supported
Basic authentication (API key)	Supported Anysphere (Cursor) Admin API Key.

Ingest from Anysphere Audit Logs in 3 steps

Note

Before starting, review the Azure Databricks user persona, supported interfaces, ingestion frequency, and common patterns.

Start ingesting from Anysphere Audit Logs

1. Configure Anysphere Audit Logs for ingestion (Admins): Set up Anysphere Audit Logs to authenticate with Azure Databricks.
2. Create a Unity Catalog connection (Admins): Create a connection in Catalog Explorer so non-admins can create pipelines.
3. Create an ingestion pipeline (Admins or non-admins): Select any supported interface and create a pipeline from an existing connection.