Pagination on audit record (/rest/api/3/auditing/record)

From the documentation I’ve noticed that the audit record list is not paginated like other resources, why is that?
There’s the “offset” parameter, but as the number of records grow some records become old (90 days?) and are discarded, so the offset is not a reliable parameter to iterate over all audit events and consume new ones as they arrive (not using a webhook)
I can implement “some sort” pagination using filters on the date, but this requires answering - can audit records come out of order? or on other words - is it safe to take the MAX timestamp from the last page as a minimal “created” filter without missing events?


1 Like