mirror of https://github.com/katanemo/plano.git synced 2026-06-17 15:25:17 +02:00

Rename all arch references to plano across the codebase

Complete rebrand from "Arch"/"archgw" to "Plano" including:
- Config files: arch_config_schema.yaml, workflow, demo configs
- Environment variables: ARCH_CONFIG_* → PLANO_CONFIG_*
- Python CLI: variables, functions, file paths, docker mounts
- Rust crates: config paths, log messages, metadata keys
- Docker/build: Dockerfile, supervisord, .dockerignore, .gitignore
- Docker Compose: volume mounts and env vars across all demos/tests
- GitHub workflows: job/step names
- Shell scripts: log messages
- Demos: Python code, READMEs, VS Code configs, Grafana dashboard
- Docs: RST includes, code comments, config references
- Package metadata: package.json, pyproject.toml, uv.lock

External URLs (docs.archgw.com, github.com/katanemo/archgw) left as-is.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-11 20:15:37 -08:00

2 KiB

Raw Blame History

Function calling

This demo shows how you can use Plano's core function calling capabilities.

Starting the demo

Please make sure the pre-requisites are installed correctly
Start Plano
```
sh run_demo.sh
```
Navigate to http://localhost:18080/
You can type in queries like "how is the weather?"

Observability

Plano gateway publishes stats endpoint at http://localhost:19901/stats. In this demo we are using prometheus to pull stats from Plano and we are using grafana to visalize the stats in dashboard. To see grafana dashboard follow instructions below,

Start grafana and prometheus using following command
```
docker compose --profile monitoring up
```
Navigate to http://localhost:3000/ to open grafana UI (use admin/grafana as credentials)
From grafana left nav click on dashboards and select "Intelligent Gateway Overview" to view Plano gateway stats

Here is a sample interaction,

Tracing

To see a tracing dashboard follow instructions below,

For Jaeger, you can either use the default run_demo.sh script or run the following command:

sh run_demo.sh jaeger

For Logfire, first make sure to add a LOGFIRE_API_KEY to the .env file. You can either use the default run_demo.sh script or run the following command:

sh run_demo.sh logfire

For Signoz, you can either use the default run_demo.sh script or run the following command:

sh run_demo.sh signoz

If using Jaeger, navigate to http://localhost:16686/ to open Jaeger UI

If using Signoz, navigate to http://localhost:3301/ to open Signoz UI

If using Logfire, navigate to your logfire dashboard that you got the write key from to view the dashboard

Stopping Demo

To end the demo, run the following command:
```
sh run_demo.sh down
```

2 KiB Raw Blame History