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
<style type='text/css'>.td1 {font-size:11pt;vertical-align:middle;text-align:left;mso-indent:0;mso-rotate:0;mso-shrinkToFit:false;mso-justifyLastLine:false;white-space:normal;mso-number-format: 'General';width: 717px;}</style>
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
Start by tracing how API responses, SSE events, and backend logs are produced for multi-step tutor or immersive generation flows. Define how one request ID is created and propagated across those three outputs, then verify that failed long-running flows can be correlated consistently in the logs and client-visible responses.
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
- Needs clarification
- Newbie friendliness
- 48/100