No 'Debug Console' output when using VSCode plus AWS Toolkit to locally create and debug Python Lambda SAM application.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 807
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 7
Description
## System details (run `AWS: About` and/or `Amazon Q: About`)
- OS: MacOS Sequoia 15.0.1 (24A348)
- Visual Studio Code version: 1.94.2
- AWS Toolkit version: v3.29.0
- Amazon Q version:
## Question
how to get the 'Debug Console' output with app specific output when locally creating and **debugging Python Lambda SAM** application ?
I am unable to get any 'Debug Console' output and all i can see is 'Output' tab full of all logs. But it isn't easy to read and debug lambda function specific logs. See attached Screenshot
**Is this a bug or I am missing some setting ?**
My SAM debug config in `launch.json`:
```
{
"configurations": [
{
"internalConsoleOptions": "openOnSessionStart",
"type": "aws-sam",
"request": "direct-invoke",
"name": "my-first-lambda-python:HelloWorldFunction",
"invokeTarget": {
"target": "template",
"templatePath": "${workspaceFolder}/my-first-lambda-python/template.yaml",
"logicalId": "HelloWorldFunction"
},
"lambda": {
"payload": {},
"environmentVariables": {}
}
}
]
}
```
Contributor guide
Research direction
Start by reproducing the direct-invoke configuration in launch.json with the stated VS Code, AWS Toolkit, macOS, and Python Lambda SAM versions. Compare the Debug Console and Output behavior, then determine whether a setting is missing or the toolkit fails to route function-specific output; done means documenting the expected behavior or adding a focused fix with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100