[GH-ISSUE #1444] Query Manager - Log export to SIEM #319

Closed
opened 2026-03-07 20:47:42 +03:00 by kerem · 4 comments
Owner

Originally created by @Sineslito on GitHub (Jan 31, 2023).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/1444

Hi! I was trying to make this to work but after reading documentation and trying some things I'm unable to workaround this.

I have Cloudbeaver AWS that has a nice feature called "Query Manager" where I can find every query of every user with results and everything, but I want to know where these are located on the instance or if there's a way to export this using something like Elastic-Search agent?

Thank you in advance!

Originally created by @Sineslito on GitHub (Jan 31, 2023). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/1444 Hi! I was trying to make this to work but after reading documentation and trying some things I'm unable to workaround this. I have Cloudbeaver AWS that has a nice feature called "Query Manager" where I can find every query of every user with results and everything, but I want to know where these are located on the instance or if there's a way to export this using something like Elastic-Search agent? Thank you in advance!
kerem 2026-03-07 20:47:42 +03:00
Author
Owner

@serge-rider commented on GitHub (Feb 1, 2023):

Hey,

In single node CloudBeaver we keepquery history in anmbedded H2 database.
You can find it in the workspace (mounted as docker volume) in subfolder .metadata/qmdb.
You can conect to this database with any client which supports JDBC and H2.

We don't keep query history as a log, they are stored in different tables.
You can join table QM_QUERY, QM_STATEMENMT, QM_EVENMT and QM_CONNECTIONto see what queries are executed in hat databases.
Or you can view users information.

If you have additional questions - please ask.

<!-- gh-comment-id:1412258188 --> @serge-rider commented on GitHub (Feb 1, 2023): Hey, In single node CloudBeaver we keepquery history in anmbedded H2 database. You can find it in the workspace (mounted as docker volume) in subfolder .metadata/qmdb. You can conect to this database with any client which supports JDBC and H2. We don't keep query history as a log, they are stored in different tables. You can join table QM_QUERY, QM_STATEMENMT, QM_EVENMT and QM_CONNECTIONto see what queries are executed in hat databases. Or you can view users information. If you have additional questions - please ask.
Author
Owner

@Gunslito commented on GitHub (Feb 8, 2023):

Thank you for your response!

I'll look into that, I can see the file but I'm not familiarized with H2 databases

<!-- gh-comment-id:1422513485 --> @Gunslito commented on GitHub (Feb 8, 2023): Thank you for your response! I'll look into that, I can see the file but I'm not familiarized with H2 databases
Author
Owner

@TatyanaSsau commented on GitHub (Apr 13, 2023):

I've noticed there is no updates for a long time. Feel free to contact me and to reopen the ticket if it's still actual.

<!-- gh-comment-id:1506590322 --> @TatyanaSsau commented on GitHub (Apr 13, 2023): I've noticed there is no updates for a long time. Feel free to contact me and to reopen the ticket if it's still actual.
Author
Owner

@Vormillion commented on GitHub (Aug 30, 2023):

What's the user and password for this H2 QMDB in Cloudbeaver EE? When I'm logging in with some random credentials it's showing only empty PUBLIC schema.

<!-- gh-comment-id:1698832241 --> @Vormillion commented on GitHub (Aug 30, 2023): What's the user and password for this H2 QMDB in Cloudbeaver EE? When I'm logging in with some random credentials it's showing only empty PUBLIC schema.
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#319
No description provided.