Building AI Products at @Sentry
San Francisco, CA
Joined November 2012
- Tweets899
- Following351
- Followers285
- Likes3.6K
Dhrumil retweeted
We pointed an agent at traces we already had.
→ ~143M fewer queries a week
→ One lookup: 935ms → 0.4ms
→ Most fixes: a line or two
Your data was the answer sheet.
blog.sentry.io/performance-w…
Dhrumil retweeted
I am here once again to say “put up or shut up”
One million to open source this year, as we continue to give back to the ecosystem via the pledge.
More than half has gone directly to your favorite open source developers.
blog.sentry.io/another-year-…
Dhrumil retweeted
I’ve moved my personal projects to Origin only (no mirror) as I am a bit of a Cursor maximalist at home.
I annoyed @brungarc to chase this integration. Wanted to “move like Cursor”: be first and iterate. Stoked that we can be there with Origin on app marketplace launch day.
When you launch anything, have your agent install and configure @Sentry.
Sentry reports frontend bugs and backend errors your users hit. You can then keep an agent watching those reports in a loop and fixing them as they come in, including while you sleep.
The free account should get you a long way toward a stable app.
Don't ever setup an alert in Sentry yourself - you can just Ask Seer
Also - you really don't need to bother querying telemetry either - It's likely that Seer will do it faster and better
Seer Agent just got a lot more powerful 💡
Now you can have the agent manage more of your Sentry projects and integrate third-party data sources, like Datadog and GCP, to help you better diagnose issues.
Learn more in the full blog post: blog.sentry.io/big-improveme…
Dhrumil retweeted
We’re also hiring engineers to help build our eval platform and enable every product team at Sentry to ship AI features with confidence: sentry.io/careers/95d2eeab-2…
We’re investing heavily in evals at @sentry. It’s early but we’re seeing a culture change from shipping vibes to shipping with clear data using our evals platform.
Will share more in a future blog post, but some stats from our devs in the past month:
- ~1800 eval runs triggered directly on PRs
- 1500 eval scenarios ran across 17 AI surfaces in our product
- Cost/token reductions of ~20-50% across a few of our surfaces
- Eval passing improvements of ~10-20% from some core “code mode” changes launching soon (shoutout @grichadev)
All this from essentially 0 back when we started this effort in May.
💯 You will encounter ppl that consider themselves to be "high agency" and think that's license to be dismissive or a jerk vs actually making things net positive
> get introduced to someone new
> being told that they are high agency
> ask if they mean breaking the rules and soiling the commons or figure out a way to push the pareto and create positive sum
> she doesn't understand: "they're high agency sir"
> meet the person
> they're soiling the commons and externalizing internalities
And be picky with captureException().
If a third-party API returns an expected, handled 401, track how often it happens as a metric. Keep it as an Error when it breaks a user flow or needs someone to fix it. Your Issues list will thank you.
Want help cleaning this up?
Use the Agent plugin and ask your coding agent to audit your Sentry calls and move routine signals to logs or metrics + build dashboards, while keeping real bugs as Issues.
docs.sentry.io/ai/agent-plug…
