Remove stuff about Spin debug logs from quickstart

Signed-off-by: itowlson <ivan.towlson@fermyon.com>
fermyon · Jan 23, 2025 · 565e47e · 565e47e
1 parent 06b20ef
commit 565e47e
Show file tree

Hide file tree

Showing 2 changed files with 15 additions and 11 deletions.
diff --git a/content/spin/v3/quickstart.md b/content/spin/v3/quickstart.md
@@ -867,16 +867,6 @@ Available Routes:
   hello-typescript: http://127.0.0.1:3000 (wildcard)
 ```
 
-If you would like to see what Spin is doing under the hood, set the RUST_LOG environment variable for detailed logs, before running `spin up`:
-
-<!-- @selectiveCpy -->
-
-```bash
-$ export RUST_LOG=spin=trace
-```
-
-> The variable is `RUST_LOG` no matter what language your application is written in, because this is setting the log level for Spin itself.
-
 Spin instantiates all components from the application manifest, and
 creates the router configuration for the HTTP trigger according to the routes in the manifest. The
 component can now be invoked by making requests to `http://localhost:3000/`
@@ -896,6 +886,8 @@ Hello, Fermyon
 
 > The `curl` output may vary based on which language SDK you use. 
 
+You'll also see any logging (stdout/stderr) from the generated code printed to the console where Spin is running. For more details, see the [page about running Spin applications](./running-apps.md).
+
 Congratulations! You just created, built and ran your first Spin application!
 
 ## Deploy Your Application to Fermyon Cloud

diff --git a/content/spin/v3/troubleshooting-application-dev.md b/content/spin/v3/troubleshooting-application-dev.md
@@ -43,4 +43,16 @@ If `spin doctor` detects a problem it can fix, you can choose to accept the fix,
 
 ## Spin Test
 
-The [spin test plugin](https://github.com/fermyon/spin-test) allows you to write test scenarios for your application's business logic. For more information, see [testing applications](./testing-apps.md).
+The [spin test plugin](https://github.com/fermyon/spin-test) allows you to write test scenarios for your application's business logic. For more information, see [testing applications](./testing-apps.md).
+
+## Viewing Spin Debug Logs
+
+If you need to follow what Spin is doing internally, set the RUST_LOG environment variable for detailed logs, before running `spin up`:
+
+<!-- @selectiveCpy -->
+
+```bash
+$ export RUST_LOG=spin=trace
+```
+
+> The variable is `RUST_LOG` no matter what language your application is written in, because this is setting the log level for Spin itself.