Point it at your own Sentry project and fire real telemetry on demand.
A React 19 app instrumented with the Sentry SDK. You paste your DSN, hit a button, and watch the event land in your own project. Six trigger types, plus a one-click sequence that fires all of them in order.
Live: https://playground-eight-lovat.vercel.app — bring your own DSN.
Personal project. Not affiliated with, endorsed by, or an official product of Sentry (the company). Just a Sentry user who wanted a clean way to demo it.
Demoing error monitoring on a customer's own project usually means breaking something real, or trusting a screenshot. This gives you a throwaway app that produces genuine events into whatever project you point it at — useful for solutions demos, onboarding a new team onto alerting, sanity-checking that a DSN is wired correctly, or seeing what an event actually looks like before you tell someone else what to expect.
| Trigger | What Sentry receives |
|---|---|
| Uncaught Exception | A raw throw escaped from the React lifecycle via setTimeout — not swallowed by an error boundary |
| Unhandled Rejection | A Promise rejected with no catch |
| Network Error | A fetch to a non-existent domain, captured explicitly and rethrown |
| Capture Message | An info-level captureMessage — no exception involved |
| Slow Transaction | A 3-second span, so you can see performance data, not just errors |
| Custom Metrics | Counters, gauges, and distributions in one shot |
Session replay is on at a 10% sample rate; tracing is at 100%.
The app lives in solar-chromosphere/ — the repo root holds only the Vercel
SPA-routing config, so deploys and local dev both work from a clean checkout.
cd solar-chromosphere
npm install
npm run dev # then open the printed localhost URL
npm run build # tsc -b && vite buildNo DSN is needed to start the app. You enter it in the UI.
Kept in localStorage on your device and used to call Sentry.init in your
browser. It is never committed, never sent anywhere except Sentry's own ingest
endpoint, and Disconnect clears it. Nothing here has a server.
A DSN is a write-only ingest key — it is safe in client-side code by design (every Sentry-instrumented web app ships one). It is not an API token and cannot read your project.
React 19 · TypeScript · Vite 7 · Tailwind 3 · React Router 7 · @sentry/react 10