[grouping info] Include Seer stacktrace string in grouping info response
Open
Nobody has claimed this yet.
Improvement
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
For debugging purposes, it would be helpful to know exactly what we sent to Seer. Probably not something we want to show in the UI, but we could include it in the JSON in the response.
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 locating the grouping info JSON response and the code that prepares the Seer stacktrace. Check how the exact submitted stacktrace is represented, then verify the response includes it for debugging without exposing it in the UI; add or run the relevant API tests if they are present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100