You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Objective of this issue is to add this new tab on path '/$organizationId/$projectId/view/audit-log:
BE:
store audit events based on graphql mutation resolver names in a single clickhouse table called audit_log
each event must include orgId, projectId, userId, userEmail
the list of events does not have to be 100% perfect-we can add or remove new events at any time in code review or later even after deployment. It should cover:
user acces and organisation membership changes
user roles
publishing of schemas
CRUD operation on projects, targets and organizations
add new GQL API resolvers to be able to select from this new table supporting all the filters listed for FE
use await for audit log insertions for all operations by default
store generated log files to s3 for users to download
FE:
Create a new page for audit log where user can:
download a CSV by clicking on a Download CSV button on this page
download a text file by clicking on a Download Plain text button on this page
see a preview list of last 30 events printed in human friendly format
We would provide these filters which apply to both download options
date range - to avoid pulling entire history of events. By default we will show events in the past week
by user - in case somebody wants to see actions made by a user
by user email - to allow searching for actions done by users who got deleted
by project - to scope down the logs to a specific project (by default audit log contains data from all projects of the org)
by target - to scope down it even more
by action - type or group of action types
The text was updated successfully, but these errors were encountered:
Objective of this issue is to add this new tab on path
'/$organizationId/$projectId/view/audit-log
:BE:
store audit events based on graphql mutation resolver names in a single clickhouse table called
audit_log
each event must include orgId, projectId, userId, userEmail
the list of events does not have to be 100% perfect-we can add or remove new events at any time in code review or later even after deployment. It should cover:
add new GQL API resolvers to be able to select from this new table supporting all the filters listed for FE
use
await
for audit log insertions for all operations by defaultstore generated log files to s3 for users to download
FE:
Create a new page for audit log where user can:
Download CSV
button on this pageDownload Plain text
button on this pageWe would provide these filters which apply to both download options
The text was updated successfully, but these errors were encountered: