(docs) proxy, show users how to use detailed_debug

docs/my-website/docs/proxy/cli.md

@@ -82,6 +82,15 @@ Cli arguments,  --host, --port, --num_workers
      litellm --debug
      ```
 
+#### --detailed_debug
+   - **Default:** `False`
+   - **Type:** `bool` (Flag)
+   - Enable debugging mode for the input.
+   - **Usage:** 
+     ```shell
+     litellm --detailed_debug
+     ``
+
 #### --temperature
    - **Default:** `None`
    - **Type:** `float`

docs/my-website/docs/simple_proxy_old_doc.md

@@ -947,6 +947,13 @@ Run the proxy with `--debug` to easily view debug logs
 litellm --model gpt-3.5-turbo --debug
 ```
 
+### Detailed Debug Logs 
+
+Run the proxy with `--detailed_debug` to view detailed debug logs
+```shell
+litellm --model gpt-3.5-turbo --detailed_debug
+```
+
 When making requests you should see the POST request sent by LiteLLM to the LLM on the Terminal output
 ```shell
 POST Request Sent from LiteLLM:
@@ -1281,6 +1288,14 @@ LiteLLM proxy adds **0.00325 seconds** latency as compared to using the Raw Open
      ```shell
      litellm --debug
      ```
+#### --detailed_debug
+   - **Default:** `False`
+   - **Type:** `bool` (Flag)
+   - Enable debugging mode for the input.
+   - **Usage:** 
+     ```shell
+     litellm --detailed_debug
+     ```
 
 #### --temperature
    - **Default:** `None`