Let Seer do more of your work in Sentry #105737
Dhrumil-Sentry
announced in
Launch Feedback
Replies: 2 comments 5 replies
-
|
Emailed |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
would love to test |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
TL;DR
The work you already do in Sentry
If you use Sentry regularly, a lot of your time goes into manual work:
This work is necessary, but time-consuming.
What Seer already does today
Seer already helps by automatically root causing issues and proposing fixes when possible.
This happens by default for many issues, without manual intervention.
What’s changing
We’re experimenting with a new way to interact with Seer that lets you direct it to take on more of this work.
Instead of manually driving every query or investigation, you can ask Seer to handle more of the analysis and triage inside Sentry.
The goal is to reduce time spent navigating data and stitching together answers.
The kinds of work Seer can do for you
With this new interaction UX, Seer can take on work you’d otherwise do manually across Sentry. You can ask follow up questions and steer it - It has access to several tools and knows how to work through your data in Sentry.
Querying and summarization
Seer can translate natural language questions into concrete queries, run them across your data, and summarize the results.
This saves you from manually constructing queries, iterating on filters, and interpreting charts.
Investigations
When you see a spike on a chart or receive an alert, you can ask Seer to investigate directly.
Seer will:
This replaces a series of manual queries and correlation steps.

Triage and prioritization
You can ask Seer to help with triage decisions, such as identifying who has the most context to fix an issue.
Seer can use stack traces, error context, recent code changes to guide prioritization.

This is early, and not everything will work well yet. We want to understand where this clearly saves time versus where it doesn’t.
Looking for early volunteers
We’re looking for early volunteers who are willing to actively use this and give feedback, not just try it once.
This is best suited for folks who:
How to get access and try it
If you’re interested:
Once you have access:
We’re especially interested in:
Beta Was this translation helpful? Give feedback.
All reactions