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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: