litellm - 💡(How to fix) Fix [Bug]: Opik: automatically use assigned opik metdata from user api key when missing in request [1 pull requests]

Check for existing issues

• I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

This is a fix for this previously implemented feature: https://github.com/BerriAI/litellm/issues/15895 After the Opik integration was revised, this feature was removed and no longer worked properly

This feature is also mentioned in the live documentation. Users are trying to get the Opik integration to work based on the documentation, but it isn't working. https://docs.litellm.ai/docs/observability/opik_integration

Purpose of this feature: Sometimes, as a LiteLLM admin, you can't control which metadata is attached to the request. Currently, the caller must select the Opik integration and the correct project themselves. The advantage of this API key integration is that the LiteLLM admin can assign requests to the correct Opik projects even if the appropriate metadata is missing from the request.

--> I will implement my previous changes to adapt them to the new code structure

Steps to Reproduce

1. Do not send opik metadata in a llm request
2. Store a metadata on a litellm api key
3. no traces in opik visible

Relevant log output

What part of LiteLLM is this about?

Proxy

What LiteLLM version are you on ?

latest

Twitter / LinkedIn details

No response