Merge branch 'master' into cursor/add-example-image-to-sentry-ios-user-feedback-page-09c2

Author: romtsn

.env.example

@@ -5,3 +5,4 @@
 
 NEXT_PUBLIC_ALGOLIA_APP_ID=
 NEXT_PUBLIC_ALGOLIA_SEARCH_KEY=
+NEXT_PUBLIC_SENTRY_DSN=

.gitignore

@@ -50,9 +50,10 @@ typings/
 # Output of 'npm pack'
 *.tgz
 
-# dotenv environment variables file
+# dotenv environment variables files
 .env
-.env.development
+.env.*
+!.env.example
 
 # gatsby files
 .cache/

develop-docs/development-infrastructure/environment/index.mdx

@@ -102,13 +102,17 @@ Just like running `sentry` (see above), you can start the `devservices` using th
 devservices up
 ```
 
-You will also need to enable workers which you can do so by running the following command:
+To run tasks, you will also need to start taskbroker:
 
 ```shell
-devservices up taskbroker
+# start just taskbroker
+devservices up --mode=taskbroker
+
+# start taskbroker and a backgrond worker
+devservices up --mode=taskworker
 ```
 
-or use a --mode that includes workers. If you use the --mode flag of devservices, any modes that started celery workers will now start taskbroker and a taskworker.
+If you use the `--mode` flag of devservices, any modes that started celery workers will now start taskbroker and a taskworker.
 
 After that, you can start the development server inside the `getsentry` folder:
 

develop-docs/development-infrastructure/environment/ports.mdx

@@ -8,28 +8,32 @@ The following is a non-exhaustive list of ports used by Sentry services or any d
 * Finding out why a port is used on your work machine and which process to kill to make it free.
 * Finding out which ports are probably safe to assign to new services.
 
-| Port | Service                                    | Description
-|:-----|:-------------------------------------------|:-----------
-| 9000 | Clickhouse                                 | <Link to="/development/devservices/">Devservice</Link> `clickhouse`. Database for Snuba.
-| 8123 | Clickhouse                                 |
-| 9009 | Clickhouse                                 |
-| 3021 | Symbolicator                               | <Link to="/development/devservices/">Devservice</Link> `symbolicator`. For processing stacktraces.
-| 1218 | [Snuba][]                                  | <Link to="/development/devservices/">Devservice</Link> `snuba`. For searching events.
-| 1219 | [Snuba][] admin                            | Not part of devservices setup, but running `snuba admin` will listen on this port.
-| 9092 | Kafka                                      | <Link to="/development/devservices/">Devservice</Link> `kafka`. for relay-sentry communication and optionally for sentry-snuba communication
-| 6379 | Redis                                      | <Link to="/development/devservices/">Devservice</Link> `redis` (or perhaps installed via Homebrew in rustier setups), responsible for caches, relay projectconfigs and Celery queues
-| 5432 | Postgres                                   | <Link to="/development/devservices/">Devservice</Link> `postgres` (or perhaps installed via Homebrew in rustier setups)
-| 7899 | [Relay][]                                  | <Link to="/development/devservices/">Devservice</Link> `relay`. Serves APIs for SDKs to send events to (aka event ingestion). Webpack on 8000 reverse-proxies to this server. Starts/stops with `sentry devserver`.
-| 8000 | <Link to="/development/environment/">Sentry Dev</Link> | Webpack devserver, routing all ingest paths to Relay, and the rest to uWSGI. Routing is defined in `webpack.config.ts` in Sentry.
-| 8001 | uWSGI                                      | Starts/stops with `sentry devserver`. Serves the Django app/API. Webpack on 8000 reverse-proxies to this server. In a siloed devserver, this port is used for control silo.
-| 8010 | uWSGI (region silo)                        | Starts/stops with `sentry devserver --silo=region`. Serves the Django app/API. Webpack on 8000 reverse-proxies to this server.
-| 7999 | Sentry frontend prod proxy                 | For testing local UI changes against a prod API
-| 8000 | [Develop docs][]                           | The website around this document. **Conflicts with Sentry Dev.**
-| 3000 | [User docs][]                              | User-facing documentation. May conflict with Relay if Relay is run outside of devservices.
-| 9001 | Sentry Dev Styleguide server               | Bound when running `sentry devserver --styleguide`
-| 9000 | `sentry run web`                           | Legacy default port for `sentry run web`, changed to 9001 to avoid conflict with Clickhouse.
-| 9001 | `sentry run web`                           | Barebones frontend without webpack or Relay. <Link to="/development/environment/">Sentry Dev</Link> is likely better. **Conflicts with Sentry Dev Styleguide server.**
-| 8000 | [Relay][] mkdocs documentation             | At some point this is going to get merged into our existing docs repos. **Conflicts with Sentry Dev.**
+| Port  | Service                                    | Description
+|:------|:-------------------------------------------|:-----------
+| 9000  | Clickhouse                                 | <Link to="/development/devservices/">Devservice</Link> `clickhouse`. Database for Snuba.
+| 9009  | Clickhouse                                 | <Link to="/development/devservices/">Devservice</Link> `clickhouse`. Database for Snuba.
+| 8123  | Clickhouse                                 |
+| 9009  | Clickhouse                                 |
+| 3021  | Symbolicator                               | <Link to="/development/devservices/">Devservice</Link> `symbolicator`. For processing stacktraces.
+| 1218  | [Snuba][]                                  | <Link to="/development/devservices/">Devservice</Link> `snuba`. For searching events.
+| 1219  | [Snuba][] admin                            | Not part of devservices setup, but running `snuba admin` will listen on this port.
+| 9092  | Kafka                                      | <Link to="/development/devservices/">Devservice</Link> `kafka`.
+| 9093  | Kafka                                      |
+| 6379  | Redis                                      | <Link to="/development/devservices/">Devservice</Link> `redis` (or perhaps installed via Homebrew in rustier setups), responsible for caches, relay projectconfigs and Celery queues
+| 5432  | Postgres                                   | <Link to="/development/devservices/">Devservice</Link> `postgres` (or perhaps installed via Homebrew in rustier setups)
+| 7899  | [Relay][]                                  | <Link to="/development/devservices/">Devservice</Link> `relay`. Serves APIs for SDKs to send events to (aka event ingestion). Webpack on 8000 reverse-proxies to this server. Starts/stops with `sentry devserver`.
+| 8000  | <Link to="/development/environment/">Sentry Dev</Link> | Webpack devserver, routing all ingest paths to Relay, and the rest to uWSGI. Routing is defined in `webpack.config.ts` in Sentry.
+| 8001  | uWSGI                                      | Starts/stops with `sentry devserver`. Serves the Django app/API. Webpack on 8000 reverse-proxies to this server. In a siloed devserver, this port is used for control silo.
+| 8010  | uWSGI (region silo)                        | Starts/stops with `sentry devserver --silo=region`. Serves the Django app/API. Webpack on 8000 reverse-proxies to this server.
+| 7999  | Sentry frontend prod proxy                 | For testing local UI changes against a prod API
+| 8000  | [Develop docs][]                           | The website around this document. **Conflicts with Sentry Dev.**
+| 3000  | [User docs][]                              | User-facing documentation. May conflict with Relay if Relay is run outside of devservices.
+| 9001  | Sentry Dev Styleguide server               | Bound when running `sentry devserver --styleguide`
+| 9000  | `sentry run web`                           | Legacy default port for `sentry run web`, changed to 9001 to avoid conflict with Clickhouse.
+| 9001  | `sentry run web`                           | Barebones frontend without webpack or Relay. <Link to="/development/environment/">Sentry Dev</Link> is likely better. **Conflicts with Sentry Dev Styleguide server.**
+| 8000  | [Relay][] mkdocs documentation             | At some point this is going to get merged into our existing docs repos. **Conflicts with Sentry Dev.**
+| 50051 | Taskbroker                                 | <Link to="/backend/application-domains/tasks/">taskbroker</Link> gRPC interface for taskbroker.
+| 8969  | Sentry Spotlight                           |
 
 ## Finding out what's running on your machine
 

develop-docs/development-infrastructure/ngrok.mdx

@@ -102,7 +102,7 @@ In two separate terminal windows, start the devserver for the control and region
 
 First, start the taskbroker:
 ```shell
-devservices up taskbroker
+devservices up --mode=taskbroker
 ```
 
 ```shell

develop-docs/ingestion/relay/relay-best-practices.mdx

@@ -16,6 +16,18 @@ Make sure changes to the event protocol and APIs are forward-compatible. Relay s
 or truncate data it does not understand. It is a supported use-case to have customers running
 outdated Relays but up-to-date SDKs.
 
+For example, `enum`s in the event protocol (or any other data type received from the SDK) need to have a catchall variant
+such that customer relays running an older version can still forward the data:
+
+```rust
+enum EventColor {
+    Red,
+    Green,
+    Blue,
+    /// Unknown color, for forward compatibility.
+    Unknown(String),
+}
+```
 
 ## Feature Gate new Functionality
 

develop-docs/sdk/data-model/event-payloads/contexts.mdx

@@ -622,6 +622,96 @@ The following example illustrates the contexts part of the <Link to="/sdk/data-m
 }
 ```
 
+## Memory Info Context
+
+The memory info context captures detailed information about memory usage and garbage collection metrics in an application at the time an event occurs. This is particularly useful for diagnosing memory-related issues in managed runtime environments.
+
+The `type` and default key is `"memory_info"`.
+
+`allocated_bytes`
+
+: Currently allocated memory.
+
+`compacted`
+
+: Boolean indicating if memory was compacted.
+
+`concurrent`
+
+: Boolean indicating if concurrent garbage collection occurred.
+
+`finalization_pending_count`
+
+: Number of objects awaiting finalization.
+
+`fragmented_bytes`
+
+: Fragmented memory that cannot be used.
+
+`heap_size_bytes`
+
+: Total heap size.
+
+`high_memory_load_threshold_bytes`
+
+: Threshold for high memory load detection.
+
+`index`
+
+: GC generation index.
+
+`memory_load_bytes`
+
+: Current memory load.
+
+`pause_durations`
+
+: Array of GC pause durations in milliseconds.
+
+`pause_time_percentage`
+
+: Percentage of time spent in GC pauses.
+
+`pinned_objects_count`
+
+: Number of pinned objects in memory.
+
+`promoted_bytes`
+
+: Bytes promoted to higher generation.
+
+`total_allocated_bytes`
+
+: Total memory allocated since start.
+
+`total_available_memory_bytes`
+
+: Total memory available to the application.
+
+`total_committed_bytes`
+
+: Total committed virtual memory.
+
+**Example Memory Info Context**
+
+```json
+{
+  "contexts": {
+    "memory_info": {
+      "type": "memory_info",
+      "allocated_bytes": 1048576,           // 1 MiB
+      "total_allocated_bytes": 9437184,     // 9 MiB
+      "heap_size_bytes": 3145728,           // 3 MiB
+      "pinned_objects_count": 150,
+      "pause_time_percentage": 25.5,
+      "compacted": true,
+      "concurrent": true,
+      "pause_durations": [10, 5, 3]
+    }
+  }
+}
+```
+
 ## Thread Pool Info Context
 
 The thread pool info context captures detailed metrics about the thread pool state at the moment an event occurs. This context is useful for investigating performance bottlenecks, thread starvation, and resource contention issues in multi-threaded applications.
@@ -669,7 +759,6 @@ The `type` and default key is `"threadpool_info"`.
 }
 ```
 
-
 ## Trace Context
 
 Additional information that allows Sentry to connect multiple transactions, spans, and/or errors into one trace. **Important:** If the trace context is missing, relay will drop the transaction.
@@ -770,6 +859,48 @@ If the route is set to a string (e.g. `"route": "foo"`), it will be normalized i
 }
 ```
 
+## Unity Context
+
+The Unity context captures Unity game engine environment details for Unity-specific issue diagnosis. This context is useful for investigating graphics issues, performance problems, version compatibility, and platform-specific behavior in Unity applications.
+
+The `type` and default key is `"unity"`.
+
+`copy_texture_support`
+
+: Graphics texture copying capabilities.
+
+`editor_version`
+
+: Unity Editor version.
+
+`install_mode`
+
+: Distribution method.
+
+`rendering_threading_mode`
+
+: Rendering pipeline configuration.
+
+`target_frame_rate`
+
+: Target FPS setting.
+
+**Example Unity Context**
+
+```json
+{
+  "contexts": {
+    "unity": {
+      "copy_texture_support": "Basic, Copy3D, DifferentTypes, TextureToRT, RTToTexture",
+      "editor_version": "2022.1.23f1",
+      "install_mode": "Store",
+      "rendering_threading_mode": "LegacyJobified",
+      "target_frame_rate": "-1",
+    }
+  }
+}
+```
+
 ## Replay Context
 
 Replay context contains the replay_id of the associated replay with the event.
@@ -959,4 +1090,4 @@ The feature flag context contains information about the flags evaluated prior to
     }
   }
 }
-```
+```