Audit log filter beyond the last 1,000 records
planned
M
Maya Margalit
Right now, the audit log only shows the latest 1000 records, and filtering applies only within those 1000. We’re planning to add an API route so that when a user filters, the frontend will send the filter to the backend, which will search across the entire audit log - not just the last 1000 entries.
The result will still show up to 1000 entries, but filtered from the full log. So for example, if a user filters by “fails,” they’ll get the latest 1000 fails overall, rather than fails just within the latest 1000 records.
M
Maya Margalit
Merged in a post:
Pagination in audit logs
I
Ian Rabinowitz
Managing data (sending and viewing) in separated blocks (pagination) in audit logs
M
Maya Margalit
marked this post as
planned
M
Mark Tarry
To expand on this - the filtering options for the audit logs seems to apply a filter after fetching the first 1,000 results.
This could mean that we only see a small(er) number of records, rather than a complete history - e.g. if there are records beyond the first 1K which would match the filter criteria.
I'd expect filtering & pagination to work together, to provide admin users with a complete list of matching records.