Skip to content

Commit c604f24

Browse files
authored
Merge pull request #1464 from itowlson/application-logs-not-debug-logs
Remove stuff about Spin debug logs from quickstart
2 parents a5ecf36 + 565e47e commit c604f24

File tree

2 files changed

+15
-11
lines changed

2 files changed

+15
-11
lines changed

content/spin/v3/quickstart.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -867,16 +867,6 @@ Available Routes:
867867
hello-typescript: http://127.0.0.1:3000 (wildcard)
868868
```
869869

870-
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`:
871-
872-
<!-- @selectiveCpy -->
873-
874-
```bash
875-
$ export RUST_LOG=spin=trace
876-
```
877-
878-
> The variable is `RUST_LOG` no matter what language your application is written in, because this is setting the log level for Spin itself.
879-
880870
Spin instantiates all components from the application manifest, and
881871
creates the router configuration for the HTTP trigger according to the routes in the manifest. The
882872
component can now be invoked by making requests to `http://localhost:3000/`
@@ -896,6 +886,8 @@ Hello, Fermyon
896886

897887
> The `curl` output may vary based on which language SDK you use.
898888
889+
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).
890+
899891
Congratulations! You just created, built and ran your first Spin application!
900892

901893
## Deploy Your Application to Fermyon Cloud

content/spin/v3/troubleshooting-application-dev.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,4 +43,16 @@ If `spin doctor` detects a problem it can fix, you can choose to accept the fix,
4343
4444
## Spin Test
4545

46-
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).
46+
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).
47+
48+
## Viewing Spin Debug Logs
49+
50+
If you need to follow what Spin is doing internally, set the RUST_LOG environment variable for detailed logs, before running `spin up`:
51+
52+
<!-- @selectiveCpy -->
53+
54+
```bash
55+
$ export RUST_LOG=spin=trace
56+
```
57+
58+
> The variable is `RUST_LOG` no matter what language your application is written in, because this is setting the log level for Spin itself.

0 commit comments

Comments
 (0)