Allow backend error logging
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
Is your feature request related to a problem? Please describe.
I cannot find out why the error happens in the backend. The only logs I see are ⇨ http server started on [::]:8080 and then the HTTP requests.
Describe the solution you'd like
Provide an environment variable to log internal backend errors.
Describe alternatives you've considered
Additional context
I want to use a podman pod. The UI only shows a 500 error, the network request fails with HTTP 503 status. I want to find out what is failing.
Contributor guide
No contributing guide indexed for this repository
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 locating the backend's existing error handling and logging entry points, then inspect how environment variables are configured. The work is done when an environment variable enables internal backend errors to appear in logs for failed requests, while the existing startup and request logging continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100