From a4cad3a6d07abfbf2a6a4d5fc32c59c89dd95632 Mon Sep 17 00:00:00 2001
From: Lucas Raschek <lucas@raschek.at>
Date: Wed, 12 Mar 2025 19:08:25 +0100
Subject: [PATCH 1/2] Documentation updates

---
 docs/my-website/docs/proxy/configs.md      | 21 +++++++++++++++++++++
 docs/my-website/docs/proxy/team_logging.md |  2 +-
 2 files changed, 22 insertions(+), 1 deletion(-)

diff --git a/docs/my-website/docs/proxy/configs.md b/docs/my-website/docs/proxy/configs.md
index efb263d344..0c8d7ac725 100644
--- a/docs/my-website/docs/proxy/configs.md
+++ b/docs/my-website/docs/proxy/configs.md
@@ -598,6 +598,12 @@ Use this if you cannot mount a config file on your deployment service (example -
 
 LiteLLM Proxy will read your config.yaml from an s3 Bucket or GCS Bucket 
 
+:::info
+
+The config.yaml will be fetched from the S3 Bucket or GCS Bucket every 10 seconds. Keep this in mind as pricing may vary based on the number of requests or data transfer out of bucket.
+
+:::
+
 <Tabs>
 <TabItem value="gcs" label="GCS Bucket">
 
@@ -640,5 +646,20 @@ docker run --name litellm-proxy \
    -p 4000:4000 \
    ghcr.io/berriai/litellm-database:main-latest
 ```
+
+If you need to set the AWS credentials, the following env vars can be used:
+
+```shell
+AWS_ACCESS_KEY_ID
+AWS_SECRET_ACCESS_KEY
+AWS_SESSION_TOKEN
+AWS_REGION_NAME
+AWS_SESSION_NAME
+AWS_PROFILE_NAME
+AWS_ROLE_NAME
+AWS_WEB_IDENTITY_TOKEN
+AWS_STS_ENDPOINT
+```
+
 </TabItem>
 </Tabs>
\ No newline at end of file
diff --git a/docs/my-website/docs/proxy/team_logging.md b/docs/my-website/docs/proxy/team_logging.md
index 779a6516b4..383c829879 100644
--- a/docs/my-website/docs/proxy/team_logging.md
+++ b/docs/my-website/docs/proxy/team_logging.md
@@ -35,7 +35,7 @@ litellm_settings:
     - team_id: "06ed1e01-3fa7-4b9e-95bc-f2e59b74f3a8"
       success_callback: ["langfuse"]
       langfuse_public_key: os.environ/LANGFUSE_PUB_KEY_2 # Project 2
-      langfuse_secret: os.environ/LANGFUSE_SECRET_2 # Project 2
+      langfuse_secret: os.environ/LANGFUSE_PRIVATE_KEY_2 # Project 2
 ```
 
 Now, when you [generate keys](./virtual_keys.md) for this team-id 

From cb360ddc802d5e9ee33e1551508926b414f784f9 Mon Sep 17 00:00:00 2001
From: Lucas Raschek <lucas@raschek.at>
Date: Wed, 12 Mar 2025 21:10:58 +0100
Subject: [PATCH 2/2] Update Team Logging Docs

---
 docs/my-website/docs/proxy/team_logging.md | 24 ++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/docs/my-website/docs/proxy/team_logging.md b/docs/my-website/docs/proxy/team_logging.md
index 383c829879..9e54b16dfe 100644
--- a/docs/my-website/docs/proxy/team_logging.md
+++ b/docs/my-website/docs/proxy/team_logging.md
@@ -30,10 +30,12 @@ litellm_settings:
   default_team_settings: 
     - team_id: "dbe2f686-a686-4896-864a-4c3924458709"
       success_callback: ["langfuse"]
+      langfuse_host: os.environ/LANGFUSE_HOST
       langfuse_public_key: os.environ/LANGFUSE_PUB_KEY_1 # Project 1
       langfuse_secret: os.environ/LANGFUSE_PRIVATE_KEY_1 # Project 1
     - team_id: "06ed1e01-3fa7-4b9e-95bc-f2e59b74f3a8"
       success_callback: ["langfuse"]
+      langfuse_host: os.environ/LANGFUSE_HOST
       langfuse_public_key: os.environ/LANGFUSE_PUB_KEY_2 # Project 2
       langfuse_secret: os.environ/LANGFUSE_PRIVATE_KEY_2 # Project 2
 ```
@@ -49,6 +51,28 @@ curl -X POST 'http://0.0.0.0:4000/key/generate' \
 
 All requests made with these keys will log data to their team-specific logging. -->
 
+### Setting Team Logging via UI
+
+You can also achieve this via the UI, by setting the Team metadata to the following:
+
+```json
+{
+  "callback_settings": {
+    "callback_vars": {
+      "langfuse_host": "<your host>",
+      "langfuse_public_key": "os.environ/LANGFUSE_PUB_KEY_1",
+      "langfuse_secret_key": "os.environ/LANGFUSE_PRIVATE_KEY_1"
+    },
+    "failure_callback": [],
+    "success_callback": [
+      "langfuse"
+    ]
+  }
+}
+```
+
+Environment Variables can be used.
+
 ## [BETA] Team Logging via API 
 
 :::info