You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Log messages are written to the extension Output channel, which you can view in vscode by visiting the "Output" panel and selecting `AWS Toolkit Logs` or `Amazon Q Logs`.
347
347
- Use the `aws.dev.logfile` setting to set the logfile path to a fixed location, so you can follow
348
-
and filter logs using shell tools like `tail` and `grep`. For example in settings.json,
349
-
```
350
-
"aws.dev.logfile": "~/awstoolkit.log",
351
-
```
352
-
then you can tail the logfile in your terminal:
353
-
```
354
-
tail -F ~/awstoolkit.log
355
-
```
348
+
and filter logs using shell tools like `tail` and `grep`.
349
+
- Note: this always logs at **debug log-level** (though you can temporarily override that from the `AWS Toolkit Logs` UI).
350
+
- Example `settings.json`:
351
+
```
352
+
"aws.dev.logfile": "~/awstoolkit.log",
353
+
```
354
+
then you can tail the logfile in your terminal:
355
+
```
356
+
tail -F ~/awstoolkit.log
357
+
```
356
358
- Use the `AWS (Developer): Watch Logs` command to watch and filter Toolkit logs (including
357
359
telemetry) in VSCode.
358
360
- Only available if you enabled "dev mode" (`aws.dev.forceDevMode` setting, see above).
0 commit comments