Rezee

What your product says, beside what you build.

Errors, traces, logs, replays, uptime and metrics from your own product, in the workspace where the fix gets planned, written and shipped. Point a Sentry SDK at a new DSN and it is already sending.

Start buildingSee pricing
4 unresolved errors

From an error to the fix, in one place.

An error is read from its stack, the commit that brought it and the logs around it; an accepted cause goes to the engineering team's Intake, with a draft fix when confidence is high. Feedback about the same problem is joined to it, so both sides are counted once.

An error, read like an engineer would.

Its stack through your source maps, the commits that touched those files, the trace it was raised in and the logs around it - each a step in the likely cause, each one a link. Accept it and the fix lands in the engineering team's Intake, with the agent's draft pull request when there is one. Ship it, and the error is watched in case it comes back.

TypeError: coupon.amount is undefined

web app · first seen after deploy 8f3c2a1 · last seen 4m ago

Engineering312 events · 48 users
Likely causeHigh confidence

8f3c2a1 reads the coupon before the cart has loaded it, so a returning customer's coupon is undefined.

  1. 1Stack of the latest event, through its source mapsapplyCoupon (src/checkout.ts:41) `total -= coupon.amount;`
  2. 2web 8f3c2a1 Apply coupons before the cart loadsBy ada; changed src/checkout.ts, which the stack runs through.
  3. 3Deploy 8f3c2a1 of web to productionThe last deploy before the error first appeared.

@fixbot drafted a fix: web#412 Load the cart before coupons (draft)

Customers and code, on one item.

When people report the problem an error is causing, the report and the error become one item - both counts, both sets of customers - and go to the team whose track it is. Requests and friction go to product, written up with options and how to build each, so the spec starts from the problem rather than the first idea.

TypeError: coupon.amount is undefined

EngineeringFiled in Web's Intake

Same problem

312 events and 14 reports across what is joined here.

Feedback themeCheckout is broken14 reports

Joined because 6 customers are in both, both are on /checkout, and at the same time

Hit the errors (6, 6 on both sides)

  • Ada Park
  • Bo Chen
  • Cy Ortiz
  • Dee Shah
  • Eli Moss
  • Fay Lund

Sent feedback (9, 6 on both sides)

  • Ada Park
  • Bo Chen
  • Cy Ortiz
  • Dee Shah
  • Eli Moss
  • Fay Lund
  • Gus Hale
  • Hana Ito
  • Ivo Reyes

Watch it run.

Uptime checks with a public status page, metrics on dashboards whose charts drop into a doc, and alerts that fire once and resolve themselves. Quotas stop at the cap rather than at an invoice, and you choose how long each kind is kept and what is scrubbed before it is.

4 monitors · status page public

Bring your next project.

Start free, with no card. Connect the agent you already use, hand it an issue, and approve its first merge today.

Start buildingSee pricing