[Feature]: Allow spend /spend/logs endpoint to accept a datetime filter for full log list

[rewbs]

The Feature

I'd like to augment the /spend/logsAPI with a time range filter that allows you to retrieve individual log entries between two datetimes.

PR here: #7956

Sidenote

Currently, the API /spend/logs accepts query parameters start_date and end_date which may, on the surface, appear to provide this functionality already. In fact they provide a different feature altogether:

• If both parameters are specified, the response is presented as a daily spend aggregate rather than a full list of log events.
• If the parameters contain a time component as well as the date, the request fails.
• If either parameter is omitted, the other is ignored.

Motivation, pitch

I'd like to process fine grained usage data based on the full content of the spend logs, which requires datetime-level filtering of those logs. Currently the only way I can do this is by querying the DB directly.

Are you a ML Ops Team?

Yes

Twitter / LinkedIn details

No response

[ishaan-jaff]

we show this on the UI now: #7952

you can use the underlying endpoint there

[rewbs]

we show this on the UI now: #7952

you can use the underlying endpoint there

Oh wow thanks, I hadn't noticed there's a whole separate (and much more intuitive) endpoint for the UI to access the logs. The issue with this one aside from the fact that it's not part of the documented API, is that it appears to return results only if prompt and response bodies are logged, which is undesirable for me (I'm only interested in the metadata).

[ishaan-jaff]

nope, my PR updates that. #7952

so from then you can just see your spend logs filtered

[rewbs]

OK I see. That'll be useful when it's merged then. Is there a rationale for implementing this in a UI-specific API rather than improving the "official" API? How stable will the UI-specific API be if I decide to integrate with it?