From 38b87a6ac068473bb5ba43b00d4a2610dde1e229 Mon Sep 17 00:00:00 2001 From: Huxing Zhang Date: Tue, 6 Jan 2026 01:06:21 +0000 Subject: [PATCH 1/5] Update README: make Jaeger section optional and add AgentScope Studio section Change-Id: Ia89adef07971514e8667a6101c1b60dc4ca88895 Co-developed-by: Cursor Co-authored-by: ralf0131 <4397305+ralf0131@users.noreply.github.com> --- README.md | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 5e9161174..2a7118d5d 100644 --- a/README.md +++ b/README.md @@ -144,7 +144,7 @@ If everything is working correctly, you should see logs similar to th } ``` -### Forwarding OTLP Data to Jaeger via LoongCollector +### (Optional) Forwarding OTLP Data to Jaeger via LoongCollector #### Launch Jaeger @@ -221,6 +221,30 @@ Access the Jaeger UI to view the collected trace data. You should no ![image.png](docs/_assets/img/quickstart-results.png) +### Using AgentScope Studio to View Tracing Data + +[AgentScope Studio](https://github.com/agentscope-ai/agentscope-studio) provides a web-based interface for visualizing and analyzing tracing data from AgentScope applications. + +#### Installation + +Install AgentScope Studio: + +```shell +pip install agentscope-studio +``` + +#### Launch AgentScope Studio + +Start the AgentScope Studio server: + +```shell +as_studio +``` + +This will launch a web interface where you can view and analyze the tracing data collected from your AgentScope applications. + +For more details, please refer to the [AgentScope Studio documentation](https://github.com/agentscope-ai/agentscope-studio). + ## Community We are looking forward to your feedback and suggestions. You can join From 84a040c2412240fccc65eb7eb61dc6a491f8c480 Mon Sep 17 00:00:00 2001 From: Huxing Zhang Date: Tue, 6 Jan 2026 01:12:33 +0000 Subject: [PATCH 2/5] Add AgentScope data export configuration to AgentScope Studio section Change-Id: I038ee5920f8d33892d1b9163b6877a235803b711 Co-developed-by: Cursor Co-authored-by: ralf0131 <4397305+ralf0131@users.noreply.github.com> --- README.md | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2a7118d5d..8d6f38cb1 100644 --- a/README.md +++ b/README.md @@ -241,7 +241,26 @@ Start the AgentScope Studio server: as_studio ``` -This will launch a web interface where you can view and analyze the tracing data collected from your AgentScope applications. +AgentScope Studio will start and display the OTLP endpoint URL (typically `http://127.0.0.1:31415`). + +#### Export AgentScope Data to AgentScope Studio + +Configure your AgentScope application to export telemetry data to AgentScope Studio using OTLP: + +```shell +export OTEL_SERVICE_NAME=my-agentscope-app +export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf +export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://127.0.0.1:31415 +export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://127.0.0.1:31415 + +loongsuite-instrument \ + --traces_exporter otlp \ + --metrics_exporter otlp \ + --service_name demo \ + python demo.py +``` + +The web interface will display the collected traces and metrics, allowing you to view and analyze the tracing data from your AgentScope applications. For more details, please refer to the [AgentScope Studio documentation](https://github.com/agentscope-ai/agentscope-studio). From c94a6c7bfa001b4940a96a68d0d3a7f5f0712945 Mon Sep 17 00:00:00 2001 From: Huxing Zhang Date: Tue, 6 Jan 2026 01:13:42 +0000 Subject: [PATCH 3/5] Fix service name consistency in AgentScope Studio configuration Change-Id: I36497b1c2c17a74b0702dc418e4f3c02dd460242 Co-developed-by: Cursor Co-authored-by: ralf0131 <4397305+ralf0131@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8d6f38cb1..c2b5808c8 100644 --- a/README.md +++ b/README.md @@ -248,7 +248,7 @@ AgentScope Studio will start and display the OTLP endpoint URL (typically `http: Configure your AgentScope application to export telemetry data to AgentScope Studio using OTLP: ```shell -export OTEL_SERVICE_NAME=my-agentscope-app +export OTEL_SERVICE_NAME=demo export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://127.0.0.1:31415 export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://127.0.0.1:31415 From 26f47cf0fdc20a94f4bbef885299030f8a2e73b5 Mon Sep 17 00:00:00 2001 From: Huxing Zhang Date: Tue, 6 Jan 2026 01:14:43 +0000 Subject: [PATCH 4/5] Clarify endpoint URL usage in AgentScope Studio configuration Change-Id: I1e715fa5ee15533a87ca8b858734e23aefd6ddc2 Co-developed-by: Cursor Co-authored-by: ralf0131 <4397305+ralf0131@users.noreply.github.com> --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c2b5808c8..fef7fcf4b 100644 --- a/README.md +++ b/README.md @@ -245,13 +245,13 @@ AgentScope Studio will start and display the OTLP endpoint URL (typically `http: #### Export AgentScope Data to AgentScope Studio -Configure your AgentScope application to export telemetry data to AgentScope Studio using OTLP: +Configure your AgentScope application to export telemetry data to AgentScope Studio using OTLP. Use the endpoint URL displayed by AgentScope Studio when it starts: ```shell export OTEL_SERVICE_NAME=demo export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf -export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://127.0.0.1:31415 -export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://127.0.0.1:31415 +export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://127.0.0.1:31415 # Use the endpoint from AgentScope Studio +export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://127.0.0.1:31415 # Use the endpoint from AgentScope Studio loongsuite-instrument \ --traces_exporter otlp \ From b489fa8cd23fe236f45fd900106f3ae4e4590b13 Mon Sep 17 00:00:00 2001 From: Huxing Zhang Date: Tue, 6 Jan 2026 01:16:15 +0000 Subject: [PATCH 5/5] Add both command-line and environment variable examples for AgentScope Studio Change-Id: I2d54f077a3fdeafcf0c4e6d82fb3ebdb9f95a39b Co-developed-by: Cursor Co-authored-by: ralf0131 <4397305+ralf0131@users.noreply.github.com> --- README.md | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index fef7fcf4b..75a2f9638 100644 --- a/README.md +++ b/README.md @@ -247,16 +247,27 @@ AgentScope Studio will start and display the OTLP endpoint URL (typically `http: Configure your AgentScope application to export telemetry data to AgentScope Studio using OTLP. Use the endpoint URL displayed by AgentScope Studio when it starts: +```shell +loongsuite-instrument \ + --traces_exporter otlp \ + --metrics_exporter otlp \ + --exporter_otlp_protocol http/protobuf \ + --exporter_otlp_endpoint http://127.0.0.1:31415 \ + --service_name demo \ + python demo.py +``` + +Alternatively, you can use environment variables: + ```shell export OTEL_SERVICE_NAME=demo export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf -export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://127.0.0.1:31415 # Use the endpoint from AgentScope Studio -export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://127.0.0.1:31415 # Use the endpoint from AgentScope Studio +export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://127.0.0.1:31415 +export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://127.0.0.1:31415 loongsuite-instrument \ --traces_exporter otlp \ --metrics_exporter otlp \ - --service_name demo \ python demo.py ```