docs team / Key Based Logging on UI

This commit is contained in:
Ishaan Jaff
2025-07-05 18:26:51 -07:00
parent dd212daa10
commit 54eb00ddfb
2 changed files with 20 additions and 3 deletions
Binary file not shown.

After

Width:  |  Height:  |  Size: 467 KiB

@@ -46,13 +46,30 @@ pip install litellm==1.74.0.post1
## Key Highlights
### Team / Key Based Logging on UI
### Azure Content Safety Guardrails
### MCP Gateway: Segregate MCP tools
### Team / Key Based Logging on UI
<Image
img={require('../../img/release_notes/team_key_logging.png')}
style={{width: '100%', display: 'block', margin: '2rem auto'}}
/>
<br />
This release brings support for Proxy Admins to configure Team/Key Based Logging Settings on the UI. This allows routing LLM request/response logs to different Langfuse/Arize projects based on the team or key.
For developers using LiteLLM, their logs are automatically routed to their specific Arize/Langfuse projects. On this release, we support the following integrations for key/team based logging:
- `langfuse`
- `arize`
- `langsmith`
### Python SDK: 2.3 Second Faster Import Times
This release brings significant performance improvements to the Python SDK with 2.3 seconds faster import times. We've refactored the initialization process to reduce startup overhead, making LiteLLM more efficient for applications that need quick initialization. This is a major improvement for applications that need to initialize LiteLLM quickly.