Merge branch 'DominikB2014/revamp-insights-docs' of github.com:getsentry/sentry-docs into DominikB2014/revamp-insights-docs

Author: DominikB2014

.github/CODEOWNERS

@@ -45,12 +45,12 @@
 
 # ###### Replays #######
 
-# /src/docs/product/session-replay/                                 @getsentry/replay
-# /src/includes/session-replay-web-report-bug.mdx                   @getsentry/replay
-# /src/platform-includes/session-replay/                            @getsentry/replay @getsentry/replay-sdk-web
-# /src/platforms/javascript/common/session-replay/                  @getsentry/replay @getsentry/replay-sdk-web
-# /src/wizard/javascript/replay-onboarding/                         @getsentry/replay @getsentry/replay-sdk-web
+# /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
 
-# /src/docs/product/dev-toolbar/                                    @getsentry/replay
+# /src/docs/product/dev-toolbar/                                    @ryan953 @jas-kas
 
 # ###### End Replays #######

.github/workflows/bump-api-schema-sha.yml

@@ -14,7 +14,7 @@ jobs:
       - uses: actions/[email protected]
       - name: Get auth token
         id: token
-        uses: actions/create-github-app-token@67e27a7eb7db372a1c61a7f9bdab8699e9ee57f7 # v1.11.3
+        uses: actions/create-github-app-token@0d564482f06ca65fa9e77e2510873638c82206f2 # v1.11.5
         with:
           app-id: ${{ vars.SENTRY_INTERNAL_APP_ID }}
           private-key: ${{ secrets.SENTRY_INTERNAL_APP_PRIVATE_KEY }}

.github/workflows/prepare-release.yml

@@ -15,7 +15,7 @@ jobs:
     steps:
       - name: Get auth token
         id: token
-        uses: actions/create-github-app-token@67e27a7eb7db372a1c61a7f9bdab8699e9ee57f7 # v1.11.3
+        uses: actions/create-github-app-token@0d564482f06ca65fa9e77e2510873638c82206f2 # v1.11.5
         with:
           app-id: ${{ vars.SENTRY_RELEASE_BOT_CLIENT_ID }}
           private-key: ${{ secrets.SENTRY_RELEASE_BOT_PRIVATE_KEY }}

develop-docs/development-infrastructure/devservices.mdx

@@ -25,6 +25,10 @@ commands:
   purge               Purge the local devservices cache
 ```
 
+## Installation
+
+Installation instructions can be found [here](https://github.com/getsentry/devservices?tab=readme-ov-file#installation).
+
 ## Viewing logs for a service
 
 ```shell

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

@@ -337,7 +337,7 @@ The SDK automatically captures HTTP Client errors and sends them to [sentry.io](
 
 The HTTP Client integration should have 3 configuration options:
 
-- `captureFailedRequests` defaults to `false` due to PII reasons.
+- `captureFailedRequests` defaults to `false` when introducing this feature due to PII reasons and can be changed to `true` in a follow up major.
   - The SDK will only capture HTTP Client errors if it is enabled.
 - `failedRequestStatusCodes` defaults to `500 - 599`, this configuration option accepts a `List` of `HttpStatusCodeRange` which is a range of HTTP status code -> `min` to `max` or a single `status_code`.
   - The SDK will only capture HTTP Client errors if the HTTP Response status code is within the defined ranges in `failedRequestStatusCodes`.
@@ -538,9 +538,9 @@ Ability for the SDK to attach request body to events and triggered during the ex
 User should be able to set a configuration option `maxRequestBodySize` to instruct SDK how big requests bodies should be attached.
 SDK controls what is an actual size in bytes for each option:
 
-- `none` (default)
+- `none`
 - `small` - `1000` bytes
-- `medium` - `10000` bytes
+- `medium` - `10000` bytes (default)
 - `always`
 
 ## Log context

develop-docs/sdk/processes/basics.mdx

@@ -32,13 +32,17 @@ When sending events just substitute `orgXXX.ingest.sentry.io` with `localhost:30
 whichever port you ended up chosing.  Also note that a local relay will out of the box
 be available via HTTP only so don't try to send HTTPS requests there.
 
-## Join us on Discord
-
-You can reach out to Sentry open source contributors and talk with other SDK maintainers on the [Sentry Discord server](https://discord.gg/sentry).
-
 ## Consult Existing SDKs
 
 While we're trying to keep the docs up to date about all important things, it's usually
 a good idea to refer to already existing Sentry SDKs for input.  In particular the
 transport design is not part of the documentation but generally quite similar between
 SDKs.
+
+## Type out context in Relay
+
+To have a better understanding of various [context](https://develop.sentry.dev/sdk/data-model/event-payloads/contexts/) our SDKs emit, any newly added context should also be typed out in [Relay](https://github.com/getsentry/relay/tree/master/relay-event-schema/src/protocol/contexts).
+
+## Join us on Discord
+
+You can reach out to Sentry open source contributors and talk with other SDK maintainers on the [Sentry Discord server](https://discord.gg/sentry).

develop-docs/self-hosted/index.mdx

@@ -41,7 +41,7 @@ sudo ./install.sh
 
 ## Required Minimum System Resources
 
-We require at least Docker 19.03.6 and Compose 2.23.2.
+We require at least Docker 19.03.6 and Compose 2.32.2.
 
 These are the minimum requirements:
 - 4 CPU Cores

develop-docs/self-hosted/troubleshooting/sentry.mdx

@@ -51,3 +51,13 @@ worker1:
 ```
 
 To see a more complete example, please see [a sample solution on our community forum](https://forum.sentry.io/t/how-to-clear-backlog-and-monitor-it/10715/14?u=byk).
+
+## Cannot Load JavaScript or CSS Files From Web Interface
+
+If you are running your Sentry instance behind a CDN like Cloudflare, Fastify, or the like, you may see some errors of invalid JavaScript or CSS files being loaded from the web interface. This is caused by some static asset files that are already optimized by the bundlers, but aren't being served with minified extensions (for example, `.min.js`). Therefore, the CDN that you are using will try to optimize the files a second time, which will result in corrupted files.
+
+Some known paths where you may see this error:
+* _static/dist/sentry/entrypoints/sentry.css
+* _static/dist/sentry/entrypoints/app.js
+
+To fix this, you can disable the auto optimization performed by your CDN.

docs/account/auth-tokens/index.mdx

@@ -47,8 +47,12 @@ User auth token permissions are customizable but cannot be edited later.
 
 ![](./img/org-auth-tokens-overview.png)
 
+<Alert>
+
 They can also be generated on certain pages of Sentry's docs if you're signed in, and by using the Sentry Wizard to configure uploading source maps.
 
+</Alert>
+
 Organization auth token names are generated for you unless you create the token through the Sentry UI. This name is only used for display purposes - it helps to identify an auth token in case you want to revoke it later. You can change the name for an organization auth token at [sentry.io](https://sentry.io) on the **Edit Auth Token** page under **Settings > Developer Settings > Auth Tokens**.
 
 For security reasons, organization auth tokens are only visible _once_, right after you create them. If you lose the auth token, you will have to create a new one. This means you can't see the full token on the overview page or on the token detail page, you can only see the last characters of the token to help identify it.

docs/concepts/search/searchable-properties/issues.mdx

@@ -4,7 +4,7 @@ description: "Learn more about searchable issue properties."
 sidebar_order: 10
 ---
 
-[Issues](/product/issues/) are an aggregate of one or more error events. Searchable issues properties include status, assignment, aggregate counts, and age. You can search by issue properties in the **Issues** page and in **Dashboards** in the widget builder, depending on your dataset selection.
+[Issues](/product/issues/) are an aggregate of one or more error events. Searchable issues properties include status, assignment, aggregate counts, and age. If you have set up [evaluation tracking for feature flags](/product/issues/issue-details/feature-flags/#evaluation-tracking), you can search for issues that have error events where the feature flag evaluated value is `true` or `false`. You can search by issue properties in the **Issues** page and in **Dashboards** in the widget builder, depending on your dataset selection.
 
 ## Searchable Properties
 
@@ -178,6 +178,12 @@ Returns issues with a matching first time seen. Syntax is the same as `age`.
 
 - **Type:** datetime
 
+### `flags`
+
+For [feature flag evaluations](/product/issues/issue-details/feature-flags/#evaluation-tracking) set to `true` or `false`, the name of the feature flag.
+
+- **Type:** boolean
+
 ### `geo.city`
 
 Full name of the city