add ability to replicate Sentry report generation for testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- observability-sre
Research direction
Start by reading the log.Field handling and the Sentry report-generation path in this repository, then review the use case described in pull request 61895. Define what the simpler report representation must expose and verify that tests can use it to reproduce what is sent to Sentry.
Written by the indexing model from the issue text.
Description
Useful for testing what gets reported to Sentry at the end of the day, based on a log.Field, such as the use case in https://github.com/sourcegraph/sourcegraph/pull/61895. Ideally we can expose a simpler struct that represents how a report shows up in Sentry.
- Dominant language
- Go
- Stars
- 13
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
More from sourcegraph/log
-
sourcegraph/log#42 · 2 reactions · 1 assignee ·
Similar issues
-
textual definition
Difficulty 1/5 Under an hour Newbie friendliness 90/100
geneontology/go-ontology#32653 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Priority/High ready-for-agent Severity/Major Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100