[Feature]: Flexibility to keep configurations and spend logs in different databases

[bansal-ankita]

The Feature

Flexibility to keep configurations and spend logs in different databases

Motivation, pitch

Our database size is growing larger due to continuously pushing logs into the LiteLLM_SpendLogs table. However, if we stop doing this, the endpoints for retrieving the spend report will no longer function. We would prefer to utilize the spend tracking endpoints provided by LiteLLM, with the logs stored in a database different from the one used for configurations.

Are you a ML Ops Team?

Yes

Twitter / LinkedIn details

No response

[krrishdholakia]

Hi @bansal-ankita interesting point - how would you suggest we handle this situation?

[bansal-ankita]

Hi @krrishdholakia It should be a configurable option, allowing users to choose whether they want separate configuration and log databases. If selected, additional details can be provided, such as using a separate database within the same PostgreSQL instance, or supporting other databases like BigQuery (BQ). This is just one possible approach; other options should also be considered.

[krrishdholakia]

what would you want here?

will help scope change for v0

[bansal-ankita]

I want to retrieve spend logs from alternative sources, such as log files or through an integration with BigQuery, rather than relying on the PostgreSQL table.