You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/product/issues/issue-details/sentry-seer/index.mdx
+12-17Lines changed: 12 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,7 @@ description: "Learn about Seer, Sentry's AI agent, and managing generative AI fe
4
4
sidebar_order: 50
5
5
---
6
6
7
-
Seer is Sentry's AI agent that powers a set of features built on generative AI and ML. You can find it in the **Solutions Hub** section of the issue details page after clicking on any error from the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page.
8
-
9
-
Once you've set up Seer, you'll be able to use the following features:
7
+
Seer is Sentry's AI agent that powers a set of features built on generative AI and ML. Once you've set up Seer, you'll be able to use the following features:
10
8
11
9
-[**Autofix**](#autofix): A collaborative workflow to find the root cause and solution of issues
12
10
-[**Issue Summary**](#issue-summary): A quick summary of issue context to help you see what's going on
@@ -17,21 +15,15 @@ Autofix and Issue Summary are currently in Beta, free of charge, for paid Sentry
17
15
18
16
</Alert>
19
17
20
-
## Issue Summary
21
-
22
-
Issue Summary provides a quick overview of an issue by highlighting key insights taken from event and issue-level metadata. You'll see a quick overview of what's going wrong, a potential cause, and if relevant, insights from trace-connected issues, all in the Solutions Hub in the sidebar:
23
-
24
-

18
+
### Autofix
25
19
26
-
## Autofix
20
+
**Autofix** uses Sentry's context (issue details, tracing data, and profiles), your codebase (integrated through GitHub), and its interactions with you to identify and reason through problems in your code. Autofix can identify the root cause and suggest a code change for fixing the issue and/or add unit tests for it.
27
21
28
22
<Alert>
29
23
30
-
Autofix replaces Suggested Fix (an earlier feature that has been sunset).
31
-
32
-
</Alert>
24
+
Autofix replaces Suggested Fix (an earlier feature that has been sunset).
33
25
34
-
**Autofix** uses Sentry's context (issue details, tracing data, and profiles), your codebase (integrated through GitHub), and its interactions with you to identify and reason through problems in your code. Autofix can identify the root cause and suggest a code change for fixing the issue and/or add unit tests for it.
26
+
</Alert>
35
27
36
28
When you start an Autofix run, you'll see the following screen, with an option to share any additional context:
37
29
@@ -55,21 +47,24 @@ You are free to edit or adjust this solution based on your own requirements and
55
47
56
48
Once the coding step is complete, you can either create a Pull Request (PR) in GitHub directly from Autofix, or create a branch and checkout the code locally if you would like to iterate further.
57
49
50
+
### Issue Summary
51
+
52
+
Issue Summary provides a quick overview of an issue by highlighting key insights taken from event and issue-level metadata. You'll see a quick overview of what's going wrong, a potential cause, and if relevant, insights from trace-connected issues.
53
+
58
54
## Data Processing for Generative AI
59
55
60
-
We use the data listed below to provide insights, analysis, and solutions for your review. Your data will not be used to train any generative AI models without your express consent and AI-generated output from your data is shown only to you, not other customers. Our generative AI features are powered by generative AI models hosted by subprocessors identified on our[subprocessor list](https://sentry.io/legal/subprocessors/). Our subprocessors are only permitted to use the data as directed by us.
56
+
We use the data listed below to provide insights, analysis, and solutions for your review. Your data will not be used to train any generative AI models without your express consent and AI-generated output from your data is shown only to you, not other customers. Our generative AI features are powered by generative AI models hosted by subprocessors identified on our[subprocessor list](https://sentry.io/legal/subprocessors/). Our subprocessors are only permitted to use the data as directed by us.
61
57
62
58
The data used for these features includes:
63
-
64
59
- Error messages
65
60
- Stack traces
66
61
- Sentry spans
67
62
- DOM interactions
68
63
- Profiles
69
64
- Relevant code from linked repositories
70
65
71
-
You can learn more about our data privacy practices[here](https://docs.sentry.io/security-legal-pii/security/ai-ml-policy/#use-of-identifying-data-for-generative-ai-features).
66
+
You can learn more about our data privacy practices[here](/security-legal-pii/security/ai-ml-policy/#use-of-identifying-data-for-generative-ai-features).
72
67
73
68
## Disabling Generative AI Features
74
69
75
-
If you don't find the Seer or Issue Summary features useful and want to disable it for all users, you can do so in your organization's settings with the "Enable Generative AI features" toggle [link](https://sentry.io/orgredirect/organizations/:orgslug/settings/#hideAiFeatures).
70
+
If you don't find Seer useful and want to disable it for all users, you can do so in your organization's settings with the "Enable Generative AI features" toggle [link](https://sentry.io/orgredirect/organizations/:orgslug/settings/#hideAiFeatures).
Copy file name to clipboardExpand all lines: docs/security-legal-pii/security/service-data-usage.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ description: "Learn about Sentry's approach to AI/ML"
6
6
7
7
## Delivering a better user experience
8
8
9
-
Sentry processes your service data, the data you configure to be collected and reported to your Sentry instance, to provide our service to you. As Sentry's service has evolved, however, prior heuristics-based approaches cannot deliver the product value we've come to expect. To train and validate models for grouping, notifications, and workflow improvements, Sentry will need access to additional [service data](https://blog.sentry.io/terms-of-service-update/) to deliver a better user experience.
9
+
Sentry processes your service data, the data you configure to be collected and reported to your Sentry instance, to provide our service to you. As Sentry’s service has evolved, however, prior heuristics-based approaches cannot deliver the product value we’ve come to expect. To train and validate models for grouping, notifications, and workflow improvements, Sentry will need access to additional [service data](https://blog.sentry.io/terms-of-service-update/) to deliver a better user experience.
10
10
11
-
You can update these settings within the "Service Data Usage" section of the Legal & Compliance page in [Sentry](https://sentry.io/orgredirect/organizations/:orgslug/settings/legal/), which is located within the "Usage & Billing" Settings.
11
+
You can update these settings within the “Service Data Usage” section of the Legal & Compliance page in [Sentry](https://sentry.io/orgredirect/organizations/:orgslug/settings/legal/), which is located within the “Usage & Billing” Settings.
12
12
13
13
### Use of non-identifying data
14
14
15
-
In accordance with our Terms of Service, Sentry may use non-identifying elements of your service data for product improvement. For example, we may aggregate web vitals data to show your site's performance against a Sentry-built benchmark. The data accessed for the benchmark cannot be linked back to any particular project or customer, making it non-identifying.
15
+
In accordance with our Terms of Service, Sentry may use non-identifying elements of your service data for product improvement. For example, we may aggregate web vitals data to show your site’s performance against a Sentry-built benchmark. The data accessed for the benchmark cannot be linked back to any particular project or customer, making it non-identifying.
0 commit comments