Merge branch 'master' of https://github.com/getsentry/sentry-docs

* 'master' of https://github.com/getsentry/sentry-docs:
  Add "Data Collected" page for Godot SDK (and more) (#13533)
  Clarify FK docs (#13562)
  Clarify db index docs (#13561)
  Remove non-functioning video embed (#13557)
  Masinette integrations elba (#13503)
  Incorporate Uptime Monitors Into The Crons Management Page (#13507)
  feat(javascript): Add "Data Collected" (#13527)
  docs(relay): remove entries that are not scrubbed by default (#13555)
  flutter: Add note to app start integration (#13479)
  ref(flutter): move custom zone handling code snippet from init to troubleshooting (#13478)
  docs(python): add uv option to python install instructions (#13510)
  add docs for supabase integration (#13545)
  feat(native): add view hierarchy to develop docs (#13544)
  feat(autofix): Update autofix images (#13540)
  Ad alerts and dashboard page to new quickstart guide (#13522)
  Add data enrichment page to new onboarding guide (#13508)
  Add first onboarding guide to docs (#13462)
  (feat) Sentry MCP Documentation  (#13524)
  feat(Capacitor): Migration guides for version 2 (#13022)
  docs(js): move API-related content from Manual Setup to APIs page (#13327)

Author: codyde

develop-docs/backend/application-domains/database-migrations/index.mdx

@@ -135,11 +135,12 @@ generally prefer that, since it averages the load out over a longer period of ti
 
 ### Indexes
 
-We prefer to create indexes on large existing tables with `CREATE INDEX CONCURRENTLY`. Our migration framework will do this automatically when creating
-a new index. Note that when `CONCURRENTLY` is used we can't run the migration in a transaction, so it's important to use `atomic = False` to run these.
+These are automatically handled by the migration framework, you can just create them on the Django model and generate the migration.
 
 When adding indexes to large tables you should use a `is_post_deployment` migration as creating the index could take longer than the migration statement timeout of 5s.
 
+Note: These are created using `CONCURRENTLY`, so it's important to not set `atomic = True` for migrations that contain indexes. This is disabled by default.
+
 ### Deleting columns
 
 This is complicated due to our deploy process. When we deploy, we run migrations, and then push out the application code, which takes a while. This means that if we just delete a column or model, then code in sentry will be looking for those columns/tables and erroring until the deploy completes. In some cases, this can mean Sentry is hard down until the deploy is finished.
@@ -419,7 +420,7 @@ This second PR will contain only the migration and related boilerplate.
 
 ### Foreign Keys
 
-Creating foreign keys is mostly fine, but for some large/busy tables like `Project`, `Group` it can cause problems due to difficulties in acquiring a lock. You can still create a Django level foreign key though, without creating a database constraint. To do so, set `db_constraint=False` when defining the key.
+Creating foreign keys is mostly fine, but for some large/busy tables like `Project` and `Group` the migration can fail due to difficulties in acquiring a lock on the table. The general procedure here is to retry the migration until it goes through - The migration framework adds a lock acquisition timeout, so it's safe to do this.
 
 ### Renaming Tables
 

develop-docs/sdk/platform-specifics/native-sdks/attachments.mdx

@@ -0,0 +1,23 @@
+---
+title: Attachments
+sidebar_order: 20
+---
+
+## View Hierarchy
+The Native SDK allows you to attach a `view-hierarchy.json` file that follows the structure described in [RFC#33](https://github.com/getsentry/rfcs/blob/main/text/0033-view-hierarchy.md). This is mainly meant for downstream SDKs (e.g., [sentry-godot](https://github.com/getsentry/sentry-godot/pull/143)).
+
+
+To add a view hierarchy attachment, the path to the file has to be configured when initializing the SDK. It will monitor the file and upload it along with any event or crash that is sent to Sentry:
+
+```c
+sentry_options_add_view_hierarchy(options, "./view-hierarchy.json");
+```
+
+
+<Alert>
+ When using `Crashpad` as the crash-capturing backend in the Native SDK, the file must have the exact name `view-hierarchy.json` to be parsed correctly by the ingestion pipeline.
+</Alert>
+
+Along with the file appearing in the _Attachments_ tab, it is visualized on the issue as such:
+
+<Include name="common-imgs/viewhierarchy-example" />

docs/organization/integrations/compliance/elba/index.mdx

@@ -0,0 +1,28 @@
+---
+title: Elba
+sidebar_order: 1
+description: "Learn about Sentry's Elba integration."
+---
+
+This integration connects Sentry with Elba's access review platform to provide organizations with a comprehensive solution for managing and reviewing user access within Sentry. 
+This helps users enhance security, ensure compliance, and improve operational efficiency by providing:
+
+- Risk Reduction: Regular access reviews help identify and eliminate unnecessary or unauthorized access, reducing the risk of data breaches and insider threats.
+- Proactive Management: Early detection of permission anomalies allows for prompt corrective actions.
+
+It connects to Sentry's API to fetch detailed information about organization members, including their roles, team memberships, and permission levels. The retrieved data is presented within Elba's platform, where administrators can systematically review each user's access rights. And, The platform analyzes user permissions to identify potential security risks, such as excessive privileges or outdated access, and provides recommendations for remediation.
+
+
+This integration is maintained and supported by Elba. For more details, or questions, feel free to contact [email protected].
+
+## Install and Configure
+
+<Alert>
+
+Sentry Owner, Manager, or Admin permissions are required to install this integration.
+
+</Alert>
+
+1. Navigate to **Settings > Integrations > Elba**
+
+2. Follow the full [Elba installation instructions](https://sentry.elba.security/install).

docs/organization/integrations/compliance/index.mdx

@@ -3,7 +3,7 @@ title: Compliance
 sidebar_order: 95
 description: "Learn more about Sentry's compliance integrations."
 ---
-
+- [Elba](/organization/integrations/compliance/elba/)
 - [Truto](/organization/integrations/compliance/truto/)
 - [Vanta](/organization/integrations/compliance/vanta/)
 - [Vanta EU](/organization/integrations/compliance/vanta-eu/)

docs/organization/integrations/index.mdx

@@ -124,6 +124,7 @@ For more details, see the [full Integration Platform documentation](/organizatio
 
 | Integration                                      | API |
 | ------------------------------------------------ | --- |
+| [Elba](/organization/integrations/compliance/elba/) | X   |
 | [Truto](/organization/integrations/compliance/truto/) | X   |
 | [Vanta](/organization/integrations/compliance/vanta/) | X   |
 | [Vanta EU](/organization/integrations/compliance/vanta-eu/) | X  |

docs/platforms/dart/guides/flutter/index.mdx

@@ -96,54 +96,6 @@ Future<void> main() async {
 }
 ```
 
-```dart {tabTitle:With custom zone}
-import 'package:flutter/widgets.dart';
-import 'package:sentry_flutter/sentry_flutter.dart';
-
-Future<void> main() async {
-  // The SDK creates it's own custom zone on web for automatic error and breadcrumb tracking on web.
-  // This could lead to zone mismatch errors if you needed to call `WidgetsBinding.ensureInitialized()` before Sentry in a cusom zone.
-  // With `Sentry.runZonedGuarded` you still get convenient auto error and breadcrumb tracking and can also call `WidgetsBinding.ensureInitialized()` before Sentry.
-  Sentry.runZonedGuarded(() async {
-    WidgetsBinding.ensureInitialized();
-
-    // Errors before init will not be handled by Sentry
-
-    await SentryFlutter.init(
-      (options) {
-        options.dsn = '___PUBLIC_DSN___';
-        // Adds request headers and IP for users, for more info visit:
-        // https://docs.sentry.io/platforms/dart/guides/flutter/data-management/data-collected/ for more info
-        options.sendDefaultPii = true;
-        // ___PRODUCT_OPTION_START___ performance
-        // Set tracesSampleRate to 1.0 to capture 100% of transactions for tracing.
-        // We recommend adjusting this value in production.
-        options.tracesSampleRate = 1.0;
-        // ___PRODUCT_OPTION_END___ performance
-        // ___PRODUCT_OPTION_START___ profiling
-        // The sampling rate for profiling is relative to tracesSampleRate
-        // Setting to 1.0 will profile 100% of sampled transactions:
-        // Note: Profiling alpha is available for iOS and macOS since SDK version 7.12.0
-        options.profilesSampleRate = 1.0;
-        // ___PRODUCT_OPTION_END___ profiling
-      },
-      appRunner: () => runApp(
-        SentryWidget(
-          child: MyApp(),
-        ),
-      ),
-    );
-  } (error, stackTrace) {
-    // Automatically sends errors to Sentry, no need to do any
-    // captureException calls on your part.
-    // On top of that, you can do your own custom stuff in this callback.
-  });
-
-  // you can also configure SENTRY_DSN, SENTRY_RELEASE, SENTRY_DIST, and
-  // SENTRY_ENVIRONMENT via Dart environment variable (--dart-define)
-}
-```
-
 ## Verify
 
 Verify that your app is sending events to Sentry by adding the following snippet, which includes an intentional error. You should see the error reported in Sentry within a few minutes.

docs/platforms/dart/guides/flutter/manual-setup.mdx

@@ -62,54 +62,6 @@ Future<void> main() async {
 }
 ```
 
-```dart {tabTitle:With custom zone}
-import 'package:flutter/widgets.dart';
-import 'package:sentry_flutter/sentry_flutter.dart';
-
-Future<void> main() async {
-  // The SDK creates it's own custom zone on web for automatic error and breadcrumb tracking on web.
-  // This could lead to zone mismatch errors if you needed to call `WidgetsBinding.ensureInitialized()` before Sentry in a cusom zone.
-  // With `Sentry.runZonedGuarded` you still get convenient auto error and breadcrumb tracking and can also call `WidgetsBinding.ensureInitialized()` before Sentry.
-  Sentry.runZonedGuarded(() async {
-    WidgetsBinding.ensureInitialized();
-
-    // Errors before init will not be handled by Sentry
-
-    await SentryFlutter.init(
-      (options) {
-        options.dsn = '___PUBLIC_DSN___';
-        // Adds request headers and IP for users, for more info visit:
-        // https://docs.sentry.io/platforms/dart/data-management/data-collected/
-        options.sendDefaultPii = true;
-        // ___PRODUCT_OPTION_START___ performance
-        // Set tracesSampleRate to 1.0 to capture 100% of transactions for tracing.
-        // We recommend adjusting this value in production.
-        options.tracesSampleRate = 1.0;
-        // ___PRODUCT_OPTION_END___ performance
-        // ___PRODUCT_OPTION_START___ profiling
-        // The sampling rate for profiling is relative to tracesSampleRate
-        // Setting to 1.0 will profile 100% of sampled transactions:
-        // Note: Profiling alpha is available for iOS and macOS since SDK version 7.12.0
-        options.profilesSampleRate = 1.0;
-        // ___PRODUCT_OPTION_END___ profiling
-      },
-      appRunner: () => runApp(
-        SentryWidget(
-          child: MyApp(),
-        ),
-      ),
-    );
-  } (error, stackTrace) {
-    // Automatically sends errors to Sentry, no need to do any
-    // captureException calls on your part.
-    // On top of that, you can do your own custom stuff in this callback.
-  });
-
-  // you can also configure SENTRY_DSN, SENTRY_RELEASE, SENTRY_DIST, and
-  // SENTRY_ENVIRONMENT via Dart environment variable (--dart-define)
-}
-```
-
 ## Verify
 
 Verify that your app is sending events to Sentry by adding the following snippet, which includes an intentional error. You should see the error reported in Sentry within a few minutes.

docs/platforms/dart/guides/flutter/troubleshooting.mdx

@@ -8,7 +8,7 @@ If you need help solving issues with Sentry's Flutter SDK, you can read the edge
 
 ## Support 16 KB Page Sizes on Android
 
-Starting with Android 15, AOSP supports devices with a 16 KB page size. If your app uses NDK libraries (directly or via an SDK), you’ll need to rebuild it for compatibility with these devices.
+Starting with Android 15, AOSP supports devices with a 16 KB page size. If your app uses NDK libraries (directly or via an SDK), you'll need to rebuild it for compatibility with these devices.
 
 Update to Sentry Flutter SDK version `8.11.0` and above order to support 16 KB page sizes on Android devices. 
 
@@ -73,6 +73,38 @@ This is an [issue](https://github.com/flutter/flutter/issues/135245) with Flutte
 
 For prior versions, you can work around this by configuring the SDK only to take screenshots when the app is in the `resumed` state. To do this, set `SentryFlutterOptions.attachScreenshotOnlyWhenResumed` to `true`.
 
+## Zone Mismatch Error on Web
+
+By default, the Sentry Flutter SDK creates a custom zone on web for automatic error and breadcrumb tracking. This can lead to zone mismatch errors when your application calls `WidgetsBinding.ensureInitialized()` before initializing Sentry.
+
+To resolve this issue, use the `Sentry.runZonedGuarded` method to initialize both your application and Sentry within the same zone. This approach ensures proper zone consistency throughout your application:
+
+```dart
+import 'package:flutter/widgets.dart';
+import 'package:sentry_flutter/sentry_flutter.dart';
+
+Future<void> main() async {
+  Sentry.runZonedGuarded(() async {
+    WidgetsBinding.ensureInitialized();
+
+    await SentryFlutter.init(
+      (options) {
+        // your config...
+      },
+      appRunner: () => runApp(
+        SentryWidget(
+          child: MyApp(),
+        ),
+      ),
+    );
+  } (error, stackTrace) {
+    // Note: Errors in this zone are already sent to Sentry automatically.
+    // This callback lets you add your own custom error handling (like logging)
+    // in addition to Sentry's reporting.
+  });
+}
+```
+
 ## Using Flutter Multi-view for Web
 
 Multi-view embedding was introduced in Flutter 3.24. You'll find a detailed guide about it in the [Flutter docs](https://docs.flutter.dev/platform-integration/web/embedding-flutter-web) .

docs/platforms/godot/configuration/options.mdx

@@ -96,6 +96,12 @@ If enabled, the SDK will attach the Godot log file to the event.
 
 </ConfigKey>
 
+<ConfigKey name="attach-screenshot">
+
+If enabled, the SDK will try to take a screenshot and attach it to the event.
+
+</ConfigKey>
+
 ## Error Logger Options
 
 <ConfigKey name="logger-enabled">

docs/platforms/godot/data-management/data-collected.mdx

@@ -0,0 +1,42 @@
+---
+title: Data Collected
+description: "See what data is collected by the Sentry SDK."
+sidebar_order: 1
+---
+
+Sentry takes data privacy very seriously and has default settings in place that prioritize data safety, especially when it comes to personally identifiable information (PII) data. When you add the Sentry SDK to your application, you allow it to collect data and send it to Sentry during the runtime of your application.
+
+The category types and amount of data collected vary, depending on the integrations you've enabled in the Sentry SDK. Here's a list of data categories the Sentry Native SDK collects:
+
+## User Information
+
+By default, the Sentry SDK doesn't send any information about users, such as email address, user ID, or username. However, if the <PlatformLink to="/configuration/options/#send-default-pii">`send_default_pii` option</PlatformLink> is enabled, Sentry backend services will infer the user's IP address based on the incoming request.
+
+You can also set user information from code:
+
+```GDScript
+var user := SentryUser.new()
+user.id = "custom_id"
+user.email = "[email protected]"
+user.username = "bob"
+user.ip_address = "127.0.0.1"
+SentrySDK.set_user(user)
+```
+
+## Device Information
+
+The Sentry SDK collects information about the device, such as the name, version and build of your operating system or Linux distribution. This information is sent to Sentry by default.
+
+## Screenshots
+
+The <PlatformLink to="/enriching-events/screenshots">screenshot feature</PlatformLink> is disabled by default. If you choose to enable this feature in options, any screenshots captured may contain sensitive data visible in the application at the time of the error.
+
+## Godot Log File
+
+By default, the Sentry SDK automatically attaches the Godot log file to events it sends. Since this log file contains all messages printed in your code and by the engine itself, it may inadvertently include sensitive information. To enhance privacy protection, you can disable the <PlatformLink to="/configuration/options/#attach-log">`attach_log` option</PlatformLink> in the Godot Project Settings.
+
+## Thread Stack Information
+
+At the time of a crash, the stack of each thread is collected and sent to Sentry as part of the Minidump snapshot for `crashpad` backend. This information is sent to Sentry by default, but dropped after processing the event in the backend.
+
+These files are not stored by default, but you can <PlatformLink to="/data-management/store-minidumps-as-attachments/">enable Minidump Storage</PlatformLink> in the Sentry organization or project settings.