Skip to main content

Trace database operations with audit logs

Audit logs help database teams answer a critical incident question quickly: who performed which operation on which database object, and when did it happen? NineData Database DevOps centralizes database access and records operations so that administrators can investigate risky or unexpected changes.

Scenario​

Consider a production incident where order data is deleted from a MySQL database. Application logs show missing order records, but they do not identify who ran the SQL. Binlog analysis can show that DELETE operations occurred, but it may still take time to connect the operation to a user.

If database access is managed through NineData, administrators can use audit logs to trace the operation back to the user, data source, database object, SQL action, and execution time.

What Audit Logs Help You Verify​

Use NineData audit logs to review:

  • The user who performed an operation.
  • The affected data source, database, table, or other object.
  • The operation type and execution time.
  • Whether the operation followed the configured database DevOps workflow.

Audit logs are most effective when they are combined with access control, SQL development policies, and approval workflows.

  1. Add company data sources to NineData so users access databases through one platform.

    Manage data sources in NineData

    Open a managed data source

  2. Configure change rules for the environment, including which operations are allowed, which require approval, and which are blocked.

    Configure SQL change rules

  3. Invite team members to NineData and assign permissions. Permissions can be controlled at a fine-grained level, including column-level access.

    Assign user permissions

  4. Require users to access production databases through NineData instead of shared direct database accounts.

Use Audit Logs During An Incident​

When an incident occurs, open the audit log page and filter by user, data source, database object, operation type, or time range.

Review database audit logs

Use the audit record to identify the operation, confirm its scope, and decide whether follow-up actions are required, such as rollback, permission adjustment, or approval-process changes.

Result​

Administrators can trace database operations from a central audit view. This reduces investigation time and helps teams enforce accountability for production database access.

Next Steps​