Merge branch 'master' of github.com:getsentry/sentry-docs into smi/sveltekit/clean-up-manual-qs

Author: inventarSarah

app/layout.tsx

@@ -58,6 +58,7 @@ export default function RootLayout({children}: {children: React.ReactNode}) {
           data-font-family="var(--font-rubik)"
           data-modal-disclaimer="Please note: This is a tool that searches publicly available sources. Do not include any sensitive or personal information in your queries. For more on how Sentry handles your data, see our [Privacy Policy](https://sentry.io/privacy/)."
           data-modal-example-questions="How to set up Sentry for Next.js?,What are tracePropagationTargets?"
+          data-user-analytics-cookie-enabled="false"
         />
       </body>
     </html>

develop-docs/backend/api/design.mdx

@@ -119,24 +119,24 @@ POST /resources/{id}
 
 ### Batch Operations
 
-Resources can get complicated when you need to expose batch operations vs single resource operations. For batch operations it is preferred to expose them as a `POST` request on the collection when possible.
+Resources can get complicated when you need to expose batch operations vs single resource operations. For batch operations it is preferred to expose them as a `PUT` request on the collection when possible.
 
 Let's say for example we have an endpoint that mutates an issue:
 
 ```
-POST /api/0/organizations/{org}/issues/{issue}/
+PUT /api/0/organizations/{org}/issues/{issue}/
 ```
 
 When designing a batch interface, we simply expose it on the collection instead of the individual resource:
 
 ```
-POST /api/0/organizations/{org}/issues/
+PUT /api/0/organizations/{org}/issues/
 ```
 
 You may also need to expose selectors on batch resources, which can be done through normal request parameters:
 
 ```
-POST /api/0/organizations/{org}/issues/
+PUT /api/0/organizations/{org}/issues/
 {
   "issues": [1, 2, 3]
 }
@@ -237,7 +237,7 @@ Expanding responses allow us to include relational information on a resource wit
 
 In general, endpoints should expose the fewest fields that will make the API usable in the general scenario. Doing one SQL request per API request is a good rule of thumb. To return information on a bounded relationship, endpoints should rely on the `expand` parameter. To return an unbounded relationship, it should be another endpoint.
 
-To take an example, let's talk about the projects list endpoint. A project belongs to an organizations but could be on multiple teams.
+To take an example, let's talk about the projects list endpoint. A project belongs to an organization but could be on multiple teams.
 
 By default, here's what the project endpoint should look like
 

develop-docs/backend/application-domains/kafka.mdx

@@ -31,8 +31,6 @@ KAFKA_CONSUMERS = {
 4. You may need to add some devserver options [here](https://github.com/getsentry/sentry/blob/master/src/sentry/runner/commands/devserver.py).
 4. Add tests for your consumer
 
-## Run the consumer in production
-1. Discuss it with SRE during their office  hours
-2. Create ops PR for adding your consumer to
-   [k8s/services/getsentry/_consumer-deployment.yaml.j2](https://github.com/getsentry/ops/blob/master/k8s/services/getsentry/_consumer-deployment.yaml.j2).
-3. In the [Sentry Consumers metrics dashboard](https://www.notion.so/sentry/Kafka-e8b4f93595684c97b01fe831fbceb0dc?pvs=4#1fa8b10e4b5d8044859ecaf559463cb0), add a new saved view for your consumer.
+## Deployment
+
+Visit the Ops repo and search for `shared_config/kafka/README.md` for a full, in-depth step-by-step guide.

develop-docs/sdk/expected-features/rate-limiting.mdx

@@ -88,7 +88,7 @@ While these [data categories](https://github.com/getsentry/relay/blob/master/rel
   - `error`: Error events.
   - `transaction`: Transaction type events.
   - `span`: Span type events.
-  - `security`: Events with event_type `csp`, `hpkp`, `expectct`, `expectstaple`
+  - `security`: Events with event_type `csp`
   - `attachment`: Attachment bytes stored (unused for rate limiting)
   - `session`: Session update events
   - `profile`: Profiling events

docs/organization/integrations/issue-tracking/incidentio/img/incidentio-alert-rule.png

@@ -13,7 +13,6 @@ This integration is maintained and supported by the company that created it. For
 <Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
-
 incident.io **won't** work with self-hosted Sentry.
 
 </Alert>
@@ -40,7 +39,7 @@ The Sentry issue is now attached to the incident:
 
 ![Incident with Sentry issue attached](./img/incidentio-attach-post.png)
 
-### In sentry.io
+### In Sentry
 
 To attach a Sentry issue to an incident in [sentry.io](https://sentry.io), navigate to a specific Sentry issue and find the "Linked Issues" section on the right panel. Click "Link incident.io issue" and select your active incident from the dropdown:
 
@@ -51,3 +50,17 @@ To attach a Sentry issue to an incident in [sentry.io](https://sentry.io), navig
 The incident's Slack channel will be updated with attached Sentry issue comments, edited comments, and when the Sentry issue is resolved:
 
 ![Synced comments from Sentry on an incident in Slack](./img/incidentio-issue-sync.png)
+
+
+## Alerting
+
+Once installed, you can also set Sentry to be an alert source for incidents.
+
+![incident.io alert setup](./img/incidentio-alert-setup.png)
+
+Afterward, within Sentry you can connect it to that newly created source in an alert rule.
+
+![incident.io alert rule](./img/incidentio-alert-rule.png)
+
+
+When the alert fires, it'll create an incident on incident.io, with all the downstream affects you set up on that side.

docs/organization/integrations/issue-tracking/incidentio/img/incidentio-alert-setup.png

@@ -5,15 +5,13 @@ description: "Learn more about Sentry's GitHub integration and how it can track
 ---
 
 There are two types of GitHub integrations, so make sure you're choosing the correct one:
-- [GitHub](#installing-github) - For regular GitHub accounts, these will have URLs like `https://github.com/org-name`. Follow the '[Installing GitHub](#installing-github)' instructions, **do not use the GitHub Enterprise integration**.
-- [GitHub Enterprise](#installing-github-enterprise) - For GitHub Enterprise Cloud or GitHub Enterprise Server instances. Some example URLs:
-  - `https://github.org-name.com`
-  - `https://github.com/enterprises/org-name`
-  - `https://org-name.ghe.com/`
+- [GitHub](#installing-github) - For individual GitHub users/organizations (as well as most GitHub Enterprise Cloud customers), so long as they are hosted on `github.com`. Follow the '[Installing GitHub](#installing-github)' instructions, **Please begin the installation from Sentry**.
 
-  These [can also be modified](https://docs.github.com/en/enterprise-cloud@latest/admin/managing-your-enterprise-account/changing-the-url-for-your-enterprise) so make sure you have have the correct URL during installation. For these accounts, follow the '[Installing GitHub Enterprise](#installing-github-enterprise)' instructions, **do not use the regular GitHub integration**.
+- [GitHub Enterprise](#installing-github-enterprise) - For GitHub Enterprise instances that **cannot be accessed from `github.com`**. Usually these will have a custom domain, for example:
+  - `https://github.example.com`
+  - `https://ghe.example.com/`
 
-## Installing GitHub
+  For these accounts, follow the '[Installing GitHub Enterprise](#installing-github-enterprise)' instructions.
 
 <Alert>
 

docs/organization/integrations/issue-tracking/incidentio/index.mdx

@@ -2,7 +2,7 @@
 title: Set Up Security Policy Reporting
 sidebar_title: Security Policy Reporting
 sidebar_order: 7500
-description: "Learn how Sentry can help manage Content-Security-Policy violations, CSP reports, Expect-CT, and HTTP Public Key Pinning (HPKP) failures here."
+description: "Learn how Sentry can help manage Content-Security-Policy violations and reports here."
 ---
 
 <Include name="platforms/security-policy-reporting/content.mdx" />

docs/organization/integrations/source-code-mgmt/github/index.mdx

@@ -2,7 +2,7 @@
 title: Set Up Security Policy Reporting
 sidebar_title: Security Policy Reporting
 sidebar_order: 7500
-description: "Learn how Sentry can help manage Content-Security-Policy violations, CSP reports, Expect-CT, and HTTP Public Key Pinning (HPKP) failures here."
+description: "Learn how Sentry can help manage Content-Security-Policy violations and reports here."
 ---
 
 <Include name="platforms/security-policy-reporting/content.mdx" />