Include project name in Database audit logs #9875
Assignees
Labels
-libs
Libraries: New libraries to be implemented
l-cloud-integration
Enso Cloud integration work
x-on-hold
Comments
radeusgd
added
-libs
4 tasks
mergify bot
pushed a commit
that referenced
this issue
May 11, 2024
- Closes #9599 - Implemented API for sending audit logs to the cloud on a background thread. - If the Postgres connection is opened through a datalink, its internal JDBC connection is replaced by a wrapper that reports executed queries to the audit log. - Also introduces `EnsoMeta` - a helper Java class that can be used in our helper libraries to access Enso types. - I have replaced the common pattern scattered throughout the codebase with calls to this 'library' to avoid repetitive code. - Refactored `Table.display` to share code between in-memory and DB - it was needed as the function stopped working for `DB_Table` after adding making the `Table` constructor `private`. - Clearer error when reading a SQLite database from a remote file (tells the user to download it first). - Follow up - correlate asset id of the data link: #9869 - Follow up - include project name (once bug is fixed): #9875 - Some problems/improvements of the audit log: - The audit log system is not yet ready for high throughput of logs #9870 - The logs may be lost if `System.exit` is used #9871
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow up of #9873
We want to include project name, e.g.
enso_dev.Base_Testsin the metadata of audit logs for Database connections.Currently this is blocked by #9845.
Once the above ticket is resolved, we should update the logic and tests.
The text was updated successfully, but these errors were encountered: