mirror of
https://github.com/dbeaver/cloudbeaver.git
synced 2026-04-25 21:56:01 +03:00
[GH-ISSUE #302] Enhance Logging of SQL Commands #81
Labels
No labels
AS
can't reproduce
can't reproduce
deployment
development
documentation
duplicate
duplicate
ee
enhancement
external
new driver
performance
pull-request
third party issue
wait for response
wait for review
wontfix
x:Oracle
x:cassandra
x:clickhouse
x:db2
x:duckdb
x:greenplum
x:h2
x:h2gis
x:hana
x:hive
x:intersystems
x:kyuubi
x:maria
x:mongo
x:mysql
x:postgresql
x:presto
x:sql server
x:sqlite
x:teradata
x:trino
xf:accessibility
xf:administration
xf:ai
xf:authentication
xf:aws
xf:commit-mode
xf:connection
xf:dark theme
xf:data editor
xf:datatransfer
xf:dba
xf:driver management
xf:erd
xf:filters
xf:i18n
xf:i18n
xf:installer
xf:json
xf:kerberos
xf:ldap
xf:local config
xf:log viewer
xf:metadata
xf:metadata editor
xf:navigator
xf:okta
xf:query manager
xf:resource manager
xf:scripts
xf:sql editor
xf:tasks
xf:ui/uix
xo: Firefox
xo:eclipse
xo:internet explorer
xo:macos
xp:major
xrn:internal
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cloudbeaver#81
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
@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.
@kseniiaguzeeva commented on GitHub (Mar 14, 2022):
The new Query manager has been implemented in the latest Cloudbeaver EE.