add realistic synthetic event generation for local testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- cli
Research direction
Start by reading the existing sentry-cli send-event workflow and compare its simple event generation with the SDK/demo apps, stored event JSON, and getsentry/seer-test-sandbox examples mentioned in the issue. Define the command's event-shape and complexity options before implementation. Done means local users can generate richer, realistic synthetic events and vary them to exercise different product UX paths.
Written by the indexing model from the issue text.
Description
add a cli workflow to generate fake but realistic Sentry events for local testing.
context from the thread:
- users want to test the local Sentry experience across different plans (for example AM1 and AM3) and see how more realistic events appear in-product
- current options are fragmented:
sentry-cli send-eventworks for simple cases, SDK/demo apps can generate traffic, some folks replay stored event JSON, andgetsentry/seer-test-sandboxhas realistic scenarios but is aimed at Seer testing
proposal:
- add an explicit
sentry-clifeature or subcommand for generating realistic synthetic events locally - support richer payloads than a single simple error message
- ideally make it easy to vary event shape / complexity so product and engineering can exercise different UX paths without building custom apps each time
prior art mentioned:
SENTRY_DSN="..." sentry-cli send-event --message "Test error from sentry-cli" --level error- small SDK-based demo/test apps
- replaying stored event JSONs
- https://github.com/getsentry/seer-test-sandbox
raised by: Jason Swartz
- Dominant language
- TypeScript
- Stars
- 121
- Forks
- 14
- Avg merge
- 22h 3m
- Merged PRs (30d)
- 94
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 getsentry/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
bug jared
-
jared
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·