Skip to content

audit: audit the audit log 🔍  #4408

Closed
@bpmct

Description

@bpmct

As we're quickly building/changing features, we need to ensure the audit log is capturing an accurate trail of user actions.

A 🦈 has caught a couple of issues, but we need to do a comprehensive list of CRUD actions (CLI and dashboard) and ensure they're being accurately represented.

The intended behavior is documented here.

Additionally, we should have a process in place for ensuring incoming features (#4125, #4311) are represented in the audit log. Can we do this via automated tests or should we build something into the product/QA process?

It's better to start thinking about this now before we introduce a lot of debt.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions