Skip to content

Create generic filter system to allow us to only export some audit logs #469

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Tracked by #682
misskniss opened this issue Mar 17, 2022 · 1 comment · Fixed by #1314
Closed
Tracked by #682

Create generic filter system to allow us to only export some audit logs #469

misskniss opened this issue Mar 17, 2022 · 1 comment · Fixed by #1314
Assignees
Labels
api Area: HTTP API
Milestone

Comments

@misskniss
Copy link

We have lots of spam in the current audit log from Open and Connect messages. While these are important to track, it is not as important for us to store and serve them from the dashboard. This would be better suited to be exported and stored in customers data lakes, rather than our production Postgres. We currently only export audit logs to users with slog via stdout, and this is hardcoded as the only option.

To support our desire to force customers to ingest the more spammy audit logs noted above, we will design an interface for exporting audit logs. This will allow us to arbitrarily export audit logs for customers specific needs.

In the beginning we will only have a slog implementation as before, but will query customers and decide which backends will have the highest leverage to support in the future.

@misskniss
Copy link
Author

I may have put this in the wrong sprint. Will cover in grooming session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Area: HTTP API
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants