Console/ SDK: No logs for 404 of API Resource in Console
Open
Nobody has claimed this yet.
🐛 bug
🛫 console
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 215
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 27
Description
I tried this:
- Request a non existing path of the API resource
curl http://127.0.0.1:60413/foo
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot GET /foo</pre>
</body>
This happened:
- No logs in Wing Console
- Looks like successful requests only are logged
I expected this:
- See all requests to the API, no matter the status code
Is there a workaround?
¯\_(ツ)_/¯
Component
SDK, Wing Console
Wing Version
0.18.4
Wing Console Version
Version 0.2.168 (0.2.168)
Node.js Version
v18.14.2
Platform(s)
MacOS
Anything else?
No response
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the provided curl request to /foo and inspect the Wing Console request logging entry point for API resources. Trace how successful requests reach the Console, then verify that a 404 response is logged as well; the work is done when requests are visible regardless of status code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100