Anysphere Audit Logs connector FAQ
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Anysphere Audit Logs ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
What tables does the connector support?
The connector supports the following Anysphere Audit Logs table:
audit_logs
For the schema of the table, see Supported source tables.
Does the connector support incremental ingestion?
Yes. The audit_logs table is ingested incrementally using the timestamp cursor field.
How much historical data is available?
Anysphere (Cursor) retains audit logs for approximately 30 days and caps the query window at 30 days. On the first pipeline run, the table will contain only audit events from the last 30 days, not a full historical archive. Subsequent incremental runs will capture new audit events as they occur.
What Anysphere (Cursor) access does the connector require?
The connector requires a Anysphere (Cursor) Team or Enterprise plan with Admin API access enabled. The Admin API is available only to Team and Enterprise plan customers.
What Anysphere (Cursor) permissions do I need?
To create the Admin API Key that the connector uses, you must be a Anysphere (Cursor) team admin. The key must be an Admin API Key (crsr_...) created in the Cursor dashboard. See Configure Anysphere (Cursor).