In the /api/v2/logs call, the “total” property currently returns the total number of logs matching the query parameters.
We rely on this value for pagination.
There is an upcoming breaking change in which “total” will no longer provide this information. The breaking changes guidance says, “please update your [pagination] logic to handle this change appropriately.”
Do you have any high level suggestions as to how to manage pagination without this value? Without it, there doesn’t seem to be any way to determine how many pages of logs might be available to view.
For instance, there doesn’t seem to be a “next” token or “more results” flag that would at least indicate that there are more results to get. That would at least enable us to render a “next page” link.
What are other folks doing here?