Audit Logging

SingleStore logs all database activities and writes the generated logs to an external location. SingleStore provides multiple logging levels, and each level provides limited or exhaustive information about user actions and database responses. This feature is useful for performing common information security tasks such as auditing, investigating suspicious activity, and validating access control policies.

Prerequisites

SingleStore version 7.3 or later
Required permissions for destination directory: Ensure that the destination directory has the required permissions to write log files. If SingleStore cannot write to a destination directory, then the database will become unresponsive.
Available disk space on log file directory: Ensure that the destination directory has enough disk space to write log files. If the disk runs out of space, the database will become unresponsive.

Audit of Automatic Rollback Events

If a CA is terminated before COMMIT, the open transaction is cleaned up and any uncommitted changes are rolled back.

The following options can be used to trace the implicit rollback however, there is no dedicated user-facing audit trail or event that explicitly records the automatic rollback:

MV_PROCESSLIST view shows active sessions with fields like TRANSACTION_STATE and ROW_LOCKS_HELD but only while the session is still alive, it does not capture events retrospectively.
Query History / MV_TRACE_EVENTS, which show query completions or failures but not the implicit rollback cleanup itself.
Audit logs, which capture executed SQL such as explicit ROLLBACK, but do not record a separate event for automatic rollback due to connection or process cleanup.
Node logs, which may show the CA failure or restart, but not an actual transaction-level rollback record.

Audit Logging

On this page

Prerequisites

Audit of Automatic Rollback Events

In this section

Was this article helpful?

On this page

Was this article helpful?