Could logs include request IDs for long agent flows?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
When a multi-step tutor or immersive generation fails, it is hard to trace through logs without a request ID. Having the same ID in API response, SSE events, and backend logs would help debugging.
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
Trace the API response, SSE event, and backend logging paths involved in multi-step tutor or immersive generation. Start by locating where requests enter and where these three outputs are produced; done means one request ID is consistently present in the API response, SSE events, and backend logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100