[GH-ISSUE #302] Enhance Logging of SQL Commands #81

Closed
opened 2026-03-07 20:44:34 +03:00 by kerem · 2 comments
Owner

Originally created by @jrhickey on GitHub (Mar 3, 2021).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/302

Is your feature request related to a problem? Please describe.
In order to use the tool in a larger enterprise that will grant users access to production resources we need to be able to track who/what/when/where.

Describe the solution you'd like
A simple feature would be to have a flag that can be enabled at the user level to enable audit logs.
The audit log should contain:
Date of the action
Who they are (username)
Database/connection they ran against
What they ran (DELETE * FROM SOME_COOL_TABLE)

Example

02-03-2021 13:43:23.003 some_username COOL_PROD_Database - DELETE * FROM SOME_COOL_TABLE
02-03-2021 13:45:23.003 some_developer COOL_DEV_Database - DELETE * FROM ANOTHER_COOL_TABLE

An option to output in JSON might be handy or long term auditing

Originally created by @jrhickey on GitHub (Mar 3, 2021). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/302 **Is your feature request related to a problem? Please describe.** In order to use the tool in a larger enterprise that will grant users access to production resources we need to be able to track who/what/when/where. **Describe the solution you'd like** A simple feature would be to have a flag that can be enabled at the user level to enable audit logs. The audit log should contain: Date of the action Who they are (username) Database/connection they ran against What they ran (DELETE * FROM SOME_COOL_TABLE) Example 02-03-2021 13:43:23.003 some_username COOL_PROD_Database - DELETE * FROM SOME_COOL_TABLE 02-03-2021 13:45:23.003 some_developer COOL_DEV_Database - DELETE * FROM ANOTHER_COOL_TABLE An option to output in JSON might be handy or long term auditing
kerem 2026-03-07 20:44:34 +03:00
Author
Owner

@serge-rider commented on GitHub (Mar 10, 2021):

This makes great sense.

CloudBeaver EE (which will be released soon) keeps all query execution history in the internal embedded database. Just like DBeaver EE does.
We'll add query manager view for query tracking.

<!-- gh-comment-id:795966620 --> @serge-rider commented on GitHub (Mar 10, 2021): This makes great sense. CloudBeaver EE (which will be released soon) keeps all query execution history in the internal embedded database. Just like DBeaver EE does. We'll add query manager view for query tracking.
Author
Owner

@kseniiaguzeeva commented on GitHub (Mar 14, 2022):

The new Query manager has been implemented in the latest Cloudbeaver EE.

<!-- gh-comment-id:1067225094 --> @kseniiaguzeeva commented on GitHub (Mar 14, 2022): The new Query manager has been implemented in the latest Cloudbeaver EE.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cloudbeaver#81
No description provided.