Fix llm_routing provider element (#382)

* Fix llm_routing provider element

We replaced provider with provider_interface to make it more clear to developers about provider api/backend being used. During that upgrade we removed support for mistral in provider to encourage developers to start using provider_interface. But this demo was not updated to use provider_interface as it was using mistral. This code change fixes it by replacing provider with provider_interface.

Signed-off-by: Adil Hafeez <adil.hafeez@gmail.com>

* fix the path

* move

* add more details

* fix

* Apply suggestions from code review

* fix

* fix

---------

Signed-off-by: Adil Hafeez <adil.hafeez@gmail.com>

demos/currency_exchange/arch_config.yaml

@@ -9,7 +9,7 @@ listener:
 llm_providers:
   - name: gpt-4o
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-4o
 
 system_prompt: |

demos/hr_agent/arch_config.yaml

@@ -7,7 +7,7 @@ listener:
 # Centralized way to manage LLMs, manage keys, retry logic, failover and limits in a central way
 llm_providers:
   - name: OpenAI
-    provider: openai
+    provider_interface: openai
     access_key: $OPENAI_API_KEY
     model: gpt-4o-mini
     default: true

demos/insurance_agent/arch_config.yaml

@@ -9,7 +9,7 @@ system_prompt: |
 
 llm_providers:
   - name: OpenAI
-    provider: openai
+    provider_interface: openai
     access_key: $OPENAI_API_KEY
     model: gpt-4o
     default: true

demos/llm_routing/README.md

@@ -1,5 +1,5 @@
 # LLM Routing
-This demo shows how you can arch gateway to manage keys and route to appropricate LLM.
+This demo shows how you can arch gateway to manage keys and route to appropriate LLM.
 
 # Starting the demo
 1. Please make sure the [pre-requisites](https://github.com/katanemo/arch/?tab=readme-ov-file#prerequisites) are installed correctly
@@ -9,11 +9,50 @@ This demo shows how you can arch gateway to manage keys and route to appropricat
    ```
 1. Navigate to http://localhost:18080/
 
+Following screen shows an example of interaction with arch gateway showing dynamic routing. You can select between different LLMs using "override model" option in the chat UI.
+
+![LLM Routing Demo](llm_routing_demo.png)
+
+You can also pass in a header to override model when sending prompt. Following example shows how you can use `x-arch-llm-provider-hint` header to override model selection,
+
+```bash
+
+$ curl --header 'Content-Type: application/json' \
+  --header 'x-arch-llm-provider-hint: ministral-3b' \
+  --data '{"messages": [{"role": "user","content": "hello"}]}' \
+  http://localhost:12000/v1/chat/completions 2> /dev/null | jq .
+{
+  "id": "xxx",
+  "object": "chat.completion",
+  "created": 1737760394,
+  "model": "ministral-3b-latest",
+  "choices": [
+    {
+      "index": 0,
+      "message": {
+        "role": "assistant",
+        "tool_calls": null,
+        "content": "Hello! How can I assist you today? Let's chat about anything you'd like. 😊"
+      },
+      "finish_reason": "stop"
+    }
+  ],
+  "usage": {
+    "prompt_tokens": 4,
+    "total_tokens": 25,
+    "completion_tokens": 21
+  }
+}
+
+```
+
 # Observability
-Arch gateway publishes stats endpoint at http://localhost:19901/stats. In this demo we are using prometheus to pull stats from arch and we are using grafana to visalize the stats in dashboard. To see grafana dashboard follow instructions below,
+Arch gateway publishes stats endpoint at http://localhost:19901/stats. In this demo we are using prometheus to pull stats from arch and we are using grafana to visualize the stats in dashboard. To see grafana dashboard follow instructions below,
 
 1. Navigate to http://localhost:3000/ to open grafana UI (use admin/grafana as credentials)
 1. From grafana left nav click on dashboards and select "Intelligent Gateway Overview" to view arch gateway stats
+1. For tracing you can head over to http://localhost:16686/ to view recent traces.
 
-# Selecting different LLM
-You can pick different LLM based on header `x-arch-llm-provider-hint` to override default LLM.
+Following is a screenshot of tracing UI showing call received by arch gateway and making upstream call to LLM,
+
+![Jaeger Tracing](jaeger_tracing_llm_routing.png)

demos/llm_routing/arch_config.yaml

@@ -9,23 +9,23 @@ listener:
 llm_providers:
   - name: gpt-4o-mini
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-4o-mini
     default: true
 
   - name: gpt-3.5-turbo-0125
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-3.5-turbo-0125
 
   - name: gpt-4o
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-4o
 
   - name: ministral-3b
     access_key: $MISTRAL_API_KEY
-    provider: mistral
+    provider_interface: mistral
     model: ministral-3b-latest
 
 tracing:

demos/multi_turn_rag_agent/arch_config.yaml

@@ -14,7 +14,7 @@ endpoints:
 llm_providers:
   - name: gpt-4o-mini
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-4o-mini
     default: true
 

demos/network_agent/arch_config.yaml

@@ -7,7 +7,7 @@ listener:
 # Centralized way to manage LLMs, manage keys, retry logic, failover and limits in a central way
 llm_providers:
   - name: OpenAI
-    provider: openai
+    provider_interface: openai
     access_key: $OPENAI_API_KEY
     model: gpt-3.5-turbo
     default: true

demos/weather_forecast/arch_config.yaml

@@ -18,18 +18,18 @@ overrides:
 llm_providers:
   - name: gpt-4o-mini
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-4o-mini
     default: true
 
   - name: gpt-3.5-turbo-0125
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-3.5-turbo-0125
 
   - name: gpt-4o
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-4o
 
 system_prompt: |

docs/source/concepts/includes/arch_config.yaml

@@ -9,7 +9,7 @@ listener:
 # Centralized way to manage LLMs, manage keys, retry logic, failover and limits in a central way
 llm_providers:
   - name: OpenAI
-    provider: openai
+    provider_interface: openai
     access_key: $OPENAI_API_KEY
     model: gpt-4o
     default: true

docs/source/guides/includes/arch_config.yaml

@@ -9,7 +9,7 @@ listener:
 # Centralized way to manage LLMs, manage keys, retry logic, failover and limits in a central way
 llm_providers:
   - name: OpenAI
-    provider: openai
+    provider_interface: openai
     access_key: $OPENAI_API_KEY
     model: gpt-4o
     default: true

tests/archgw/arch_config.yaml

@@ -14,18 +14,18 @@ endpoints:
 llm_providers:
   - name: gpt-4o-mini
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-4o-mini
     default: true
 
   - name: gpt-3.5-turbo-0125
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-3.5-turbo-0125
 
   - name: gpt-4o
     access_key: $OPENAI_API_KEY
-    provider: openai
+    provider_interface: openai
     model: gpt-4o
 
 system_prompt: |