Merge branch 'master' of github.com:getsentry/sentry-docs into smi/quick-start/sveltekit-manual

Author: inventarSarah

.github/CODEOWNERS

@@ -1,53 +1,47 @@
 # https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners#codeowners-syntax
 
+# See https://github.com/getsentry/sentry-docs/pull/13662 on how commented codeowners are tagged
+
 # Requiring review from security team for Content-Security-Policy changes
 **/vercel.json @getsentry/security
 
 # Codeowners listed below are used as a reference for the Sentry team to know who to contact for a given area of the codebase.
 
-# /src/platforms/android/ @getsentry/team-mobile-core
-# /src/wizard/android/ @getsentry/team-mobile-core
-# /src/platforms/apple/ @getsentry/team-mobile-core
-# /src/wizard/apple/ @getsentry/team-mobile-core
-# /src/platforms/dart/guides/flutter/ @getsentry/team-mobile-cross-platform
-# /src/wizard/flutter/ @getsentry/team-mobile-cross-platform
-# /src/platforms/dart/ @getsentry/team-mobile-cross-platform
-# /src/wizard/dart/ @getsentry/team-mobile-cross-platform
-# /src/platforms/react-native/ @getsentry/team-mobile-cross-platform
-# /src/wizard/react-native/ @getsentry/team-mobile-cross-platform
-# /src/platforms/unity/ @getsentry/team-mobile-cross-platform
-# /src/wizard/unity/ @getsentry/team-mobile-cross-platform
-# /src/wizard/cordova/ @getsentry/team-mobile-cross-platform
-
-# /src/platforms/dotnet/ @getsentry/team-mobile-cross-platform
-# /src/wizard/dotnet/ @getsentry/team-mobile-cross-platform
-# /src/platforms/java/ @getsentry/team-mobile-core
-# /src/wizard/java/ @getsentry/team-mobile-core
-
-# /src/platforms/native/ @getsentry/owners-native
-# /src/wizard/native/ @getsentry/owners-native
-# /src/wizard/minidump/ @getsentry/owners-native
-# /src/platforms/rust/ @getsentry/owners-native
-# /src/wizard/rust/ @getsentry/owners-native
-
-# /src/docs/product/discover-queries/ @getsentry/visibility
-# /src/docs/product/insights/ @getsentry/insights
-
-# /src/docs/cli/dif.mdx @getsentry/owners-native
+# /docs/platforms/android/ @getsentry/team-mobile-core
+# /docs/platforms/apple/ @getsentry/team-mobile-core
+# /docs/platforms/dart/ @getsentry/team-mobile-cross-platform
+# /docs/platforms/react-native/ @getsentry/team-mobile-cross-platform
+# /docs/platforms/javascript/guides/cordova/ @getsentry/team-mobile-cross-platform
+
+# /docs/platforms/dotnet/ @getsentry/gdx
+# /docs/platforms/godot/ @getsentry/gdx
+# /docs/platforms/nintendo-switch/ @getsentry/gdx
+# /docs/platforms/playstation/ @getsentry/gdx
+# /docs/platforms/powershell/ @getsentry/gdx
+# /docs/platforms/unity/ @getsentry/gdx
+# /docs/platforms/unreal/ @getsentry/gdx
+# /docs/platforms/xbox/ @getsentry/gdx
+
+# /docs/platforms/java/ @getsentry/team-web-sdk-backend
+# /docs/platforms/native/ @getsentry/product-owners-sdks-native
+# /docs/platforms/rust/ @getsentry/team-web-sdk-backend
+
+# /docs/product/explore/discover-queries/ @getsentry/visibility
+# /docs/product/insights/ @getsentry/insights
+
+# /docs/cli/ @getsentry/team-web-sdk-backend
 
 # /.github/labels.yml @getsentry/dev-infra
 # /.github/workflows/react-to-product-owners-yml-changes.yml @getsentry/dev-infra
-# /bin/react-to-product-owners-yml-changes.py @getsentry/dev-infra
-# /bin/react-to-product-owners-yml-changes.sh @getsentry/dev-infra
 
 # ###### Replays #######
 
-# /src/docs/product/session-replay/web                              @jas-kas @getsentry/replay-sdk-web @getsentry/replay-frontend @getsentry/replay-backend
-# /src/docs/product/session-replay/mobile                           @jas-kas @getsentry/replay-sdk-mobile @getsentry/replay-frontend @getsentry/replay-backend
-# /src/includes/session-replay-web-report-bug.mdx                   @getsentry/replay-sdk-web
-# /src/platform-includes/session-replay/                            @getsentry/replay-sdk-web @getsentry/replay-sdk-mobile
-# /src/platforms/javascript/common/session-replay/                  @getsentry/replay-sdk-web
+# /docs/product/explore/session-replay/web                              @jas-kas @getsentry/replay-sdk-web @getsentry/replay-frontend @getsentry/replay-backend
+# /docs/product/explore/session-replay/mobile                           @jas-kas @getsentry/replay-sdk-mobile @getsentry/replay-frontend @getsentry/replay-sdk-mobile
+# /includes/session-replay-web-report-bug.mdx                   @getsentry/replay-sdk-web
+# /platform-includes/session-replay/                            @getsentry/replay-sdk-web @getsentry/replay-sdk-mobile
+# /docs/platforms/javascript/common/session-replay/                  @getsentry/replay-sdk-web
 
-# /src/docs/product/dev-toolbar/                                    @ryan953 @jas-kas
+# /docs/product/sentry-toolbar/                                    @ryan953 @jas-kas
 
 # ###### End Replays #######

.github/workflows/codeowner_assignment.yaml

@@ -48,6 +48,13 @@ jobs:
           echo "Changed files:"
           echo "$CHANGED_FILES" | tr ' ' '\n' | sed 's/^/- /'
           echo "----------------------------------------"
+          
+          # Get existing reviewers
+          # merge reqeusted teams and users into a single array
+          REQUESTED_REVIEWERS=$(gh pr view $PR_NUMBER --json reviewRequests --jq '[.reviewRequests[] | if .__typename == "Team" then .slug else .login end]')
+          echo "Requested reviewers:"
+          echo "$REQUESTED_REVIEWERS" | tr ' ' '\n' | sed 's/^/- /'
+          echo "----------------------------------------"
 
           # Parse CODEOWNERS and find commented lines
           # Add newline to the end of the file if it doesn't have one, otherwise sed will not read the last line
@@ -85,8 +92,12 @@ jobs:
                     for REVIEWER in $REVIEWERS; do
                       # Remove @ symbol from reviewer name
                       REVIEWER_NAME=${REVIEWER#@}
-                      echo " - Assigning $REVIEWER_NAME to review changes in $FILE"
-                      gh pr edit $PR_NUMBER --add-reviewer "$REVIEWER_NAME"
+                      if [[ "$REQUESTED_REVIEWERS" == *"$REVIEWER_NAME"* ]]; then
+                        echo " - $REVIEWER_NAME is already a requested reviewer, skipping"
+                      else
+                        echo " - Assigning $REVIEWER_NAME to review changes in $FILE"
+                        gh pr edit $PR_NUMBER --add-reviewer "$REVIEWER_NAME"
+                      fi
                     done
                   fi
                 else
@@ -98,8 +109,12 @@ jobs:
                     for REVIEWER in $REVIEWERS; do
                       # Remove @ symbol from reviewer name
                       REVIEWER_NAME=${REVIEWER#@}
-                      echo " - Assigning $REVIEWER_NAME to review changes in $FILE"
-                      gh pr edit $PR_NUMBER --add-reviewer "$REVIEWER_NAME"
+                      if [[ "$REQUESTED_REVIEWERS" == *"$REVIEWER_NAME"* ]]; then
+                        echo " - $REVIEWER_NAME is already a requested reviewer, skipping"
+                      else
+                        echo " - Assigning $REVIEWER_NAME to review changes in $FILE"
+                        gh pr edit $PR_NUMBER --add-reviewer "$REVIEWER_NAME"
+                      fi
                     done
                   fi
                 fi
@@ -111,8 +126,12 @@ jobs:
                   for REVIEWER in $REVIEWERS; do
                     # Remove @ symbol from reviewer name
                     REVIEWER_NAME=${REVIEWER#@}
-                    echo " - Assigning $REVIEWER_NAME to review changes in $FILE"
-                    gh pr edit $PR_NUMBER --add-reviewer "$REVIEWER_NAME"
+                    if [[ "$REQUESTED_REVIEWERS" == *"$REVIEWER_NAME"* ]]; then
+                      echo " - $REVIEWER_NAME is already a requested reviewer, skipping"
+                    else
+                      echo " - Assigning $REVIEWER_NAME to review changes in $FILE"
+                      gh pr edit $PR_NUMBER --add-reviewer "$REVIEWER_NAME"
+                    fi
                   done
                 fi
               fi

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

@@ -436,6 +436,10 @@ GPU context describes the GPU of the device.
 
 Examples: `"Apple Metal"` or `"Direct3D11"`
 
+`driver_version`
+
+: _Optional_. The driver version of the graphics device.
+
 `multi_threaded_rendering`
 
 : _Optional_. Whether the GPU has multi-threaded rendering or not.
@@ -744,6 +748,49 @@ envelope endpoint.
 }
 ```
 
+## Page Context
+
+Page context contains information about the page that the event occurred on.
+
+`url`
+
+: **Required.** The URL of the page that the event occurred on, excluding query parameters & fragment.
+
+- Example: `https://sentry.io/issues`
+
+`http.query`
+
+: **Optional.** The query parameters of the page that the event occurred on.
+
+- Example: `?page=1`
+
+`http.fragment`
+
+: **Optional.** The fragment of the page that the event occurred on.
+
+- Example: `#123`
+
+`referer`
+
+: _Optional_. The referer of the page that the event occurred on.
+
+- Example: `https://sentry.io/`
+
+**Example Page Context**
+
+```json
+{
+  "contexts": {
+    "page": {
+      "url": "https://sentry.io/issues",
+      "http.query": "?page=1",
+      "http.fragment": "#123",
+      "referer": "https://sentry.io/"
+    }
+  }
+}
+```
+
 ## Response Context
 
 Response context contains information about the HTTP response associated with the event.
@@ -795,7 +842,7 @@ The required field is `package` which should contain the package or framework wh
   "contexts": {
     "missing_instrumentation": {
       "package": "express",
-      "javascript.is_cjs": true,
+      "javascript.is_cjs": true
     }
   }
 }

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

@@ -199,7 +199,7 @@ of an Xcode build or the version code of an Android build.
 
 `tags`
 
-_Optional_. A map or list of tags for this event. Each tag must be less than 200 characters.
+_Optional_. A map or list of tags for this event. Tags must have string values, and each tag must be less than 200 characters.
 
   ```json
   {

develop-docs/sdk/data-model/event-payloads/properties/tags.mdx

@@ -1,6 +1,6 @@
 `tags`
 
-: _Optional_. A map or list of tags for this event. Each tag must be less than 200 characters.
+: _Optional_. A map or list of tags for this event. Tags must have string values, and each tag must be less than 200 characters.
 
   ```json
   {

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

@@ -4,9 +4,8 @@ sidebar_order: 8
 ---
 
 The Request interface contains information on a HTTP request related to the
-event. In client SDKs, this can be an outgoing request, or the request that
-rendered the current web page. On server SDKs, this could be the incoming web
-request that is being handled.
+event. In client SDKs, this can be an outgoing request (use the [page context](../contexts/#page-context) to track the page that the request was made from).
+On server SDKs, this could be the incoming web request that is being handled.
 
 The data variable should only contain the request body (not the query string).
 It can either be a dictionary (for standard HTTP requests) or a raw request

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

@@ -139,7 +139,7 @@ _Optional_. Describes the `status` of the Span/Transaction.
 
 `tags`
 
-_Optional_. A map or list of tags for this event. Each tag must be less than 200 characters.
+_Optional_. A map or list of tags for this event. Tags must have string values, and each tag must be less than 200 characters.
 
   ```json
   {

develop-docs/sdk/expected-features/index.mdx

@@ -326,7 +326,6 @@ If Performance Monitoring is both supported by the SDK and enabled in the client
 - operation: `http.client`
 - description: `$METHOD $url` (uppercase HTTP method), e.g. `GET https://sentry.io`
 - HTTP requests must be enhanced with a [`sentry-trace` HTTP header](/sdk/telemetry/traces/#header-sentry-trace) to support [distributed tracing](https://docs.sentry.io/product/sentry-basics/tracing/distributed-tracing)
-- HTTP requests must be enhanced with a [`traceparent` HTTP header](/sdk/telemetry/traces/#header-traceparent) to support [distributed tracing](https://docs.sentry.io/product/sentry-basics/tracing/distributed-tracing)
 - HTTP requests must be enhanced with a [`baggage` HTTP header](/sdk/telemetry/traces/dynamic-sampling-context/#baggage-header) to support [dynamic sampling](/sdk/telemetry/traces/dynamic-sampling-context/)
 - span status must match HTTP response status code ([see Span status to HTTP status code mapping](/sdk/data-model/event-payloads/span/))
 - when network error occurs, span status must be set to `internal_error`

develop-docs/sdk/telemetry/logs.mdx

@@ -47,7 +47,7 @@ The `log` envelope item payload is a JSON object that represents a Sentry Log.
       "value": "User %s has logged in!",
       "type": "string"
     },
-    "sentry.message.parameters.0": {
+    "sentry.message.parameter.0": {
       "value": "John",
       "type": "string"
     },
@@ -226,17 +226,10 @@ logger()->info('Adding item %s for user %s', [$item_id, $user_id], ['extra' => 1
 ```java
 import io.sentry.Sentry;
 
-// example with MessageFormat based string template
-Sentry.logger().info("Adding item {0,string} for user {1,string}", item_id, user_id, log -> {
-  log.setAttribute("extra", 123);
-});
+Sentry.logger().info("Adding item %s for user %s", itemId, userId);
 
 // Kotlin
-Sentry.Logger.info("Adding item for user") { // fun info(block: LogItem.() -> Unit)
-  setAttribute("item_id", item_id)
-  setAttribute("user_id", user_id)
-  setAttribute("extra", 123)
-}
+Sentry.logger().info("Adding item %s for user %s", itemId, userId)
 ```
 
 #### Apple

develop-docs/sdk/telemetry/traces/distributed-tracing/index.mdx

@@ -6,18 +6,16 @@ This document describes how an SDK should propagate information between differen
 
 For an overview see [Distributed Tracing](https://docs.sentry.io/product/performance/distributed-tracing/) in the product docs.
 
-Sentry uses three containers to hold trace information [`sentry-trace`](/sdk/performance/#header-sentry-trace), [`traceparent`](/sdk/performance/#header-traceparent) and [`baggage`](/sdk/performance/dynamic-sampling-context/#baggage-header).
+Sentry uses two containers to hold trace information [`sentry-trace`](/sdk/performance/#header-sentry-trace) and [`baggage`](/sdk/performance/dynamic-sampling-context/#baggage-header).
 
 With these containers you can propagate a trace to a down-stream service by either:
-- adding `sentry-trace`, `traceparent` and `baggage` HTTP headers (when making outgoing HTTP requests),
-- adding `sentry-trace`, `traceparent` and `baggage` as meta data (when putting tasks into a queue, details are specific to the queue you want to support), or
-- setting environment variables (when calling another process). In this case the env variables should be called `SENTRY_TRACE`, `SENTRY_TRACEPARENT` and `SENTRY_BAGGAGE`.
+- adding `sentry-trace` and `baggage` HTTP headers (when making outgoing HTTP requests),
+- adding `sentry-trace` and `baggage` as meta data (when putting tasks into a queue, details are specific to the queue you want to support), or
+- setting environment variables (when calling another process). In this case the env variables should be called `SENTRY_TRACE` and `SENTRY_BAGGAGE`.
 
 The SDK running in the receiving service needs to make sure to pick up incoming trace information by
-- reading `sentry-trace`, `traceparent` and `baggage` headers for each incoming HTTP request,
-- reading `sentry-trace`, `traceparent` and `baggage` meta data when retrieving an item from a queue, or
-- reading the environment variables `SENTRY_TRACE`, `SENTRY_TRACEPARENT` and `SENTRY_BAGGAGE` on startup.
-
-In case both `sentry-trace` and `traceparent` are present, `sentry-trace` takes precedence.
+- reading `sentry-trace` and `baggage` headers for each incoming HTTP request,
+- reading `sentry-trace` and `baggage` meta data when retrieving an item from a queue, or
+- reading the environment variables `SENTRY_TRACE` and `SENTRY_BAGGAGE` on startup.
 
 This trace information should be stored in the "propagation context" of the current scope. This makes sure that all telemetry that is emitted from the receiving service to Sentry will include the correct trace information.