Starburst (Trino) Audit Logs
Deprecation notice
Support for the audit endpoint and UI has been deprecated. Instead, pull audit logs from Kubernetes and push them to your SIEM.
With the Event Listener enabled, users can view audit records for queries made in Starburst against Immuta data sources on the Audit page. Immuta audits the activity of Immuta users on Immuta data sources.
Requirements
Starburst (Trino) users registered as Immuta users: Note that the users' Starburst (Trino) usernames must be mapped to Immuta. Without this, Immuta will not know the users are Immuta users and will not collect audit events for their data access activity.
Best Practices: Store Audit Records
By default Immuta audit records expire after 60 days, so store audit records outside of Immuta in order to retain the audits long term.
Audit Message
Each audit message from the Immuta platform will be a one-line JSON object containing the properties listed below. These audit records are stored with the recordType
: prestoQuery
.
Property | Description | Example |
---|---|---|
ID |
|
|
DateTime |
|
|
Month |
|
|
ProfileID |
|
|
UserID |
|
|
DataSourceID |
|
|
DataSourceName |
|
|
ProjectID |
|
|
ProjectName |
|
|
RecordType |
| Trino query audit records will always be |
Success |
|
|
Component |
|
|
AccessType |
|
|
Query |
|
|
Extra |
| See example audit record below. |
DataSourceSchemaName |
| The name of the schema that the data source that was queried came from. |
DataSourceTableName |
|
|
sqlUser |
|
|
Example Audit Record
Last updated