Merge branch 'master' into sergiydybskiy/remove-sticky-from-onboarding-options-on-mobile

Author: sergical

app/[[...path]]/page.tsx

@@ -47,7 +47,12 @@ export const dynamic = 'force-static';
 const mdxComponentsWithWrapper = mdxComponents(
   {Include, PlatformContent},
   ({children, frontMatter, nextPage, previousPage}) => (
-    <DocPage frontMatter={frontMatter} nextPage={nextPage} previousPage={previousPage}>
+    <DocPage
+      frontMatter={frontMatter}
+      nextPage={nextPage}
+      previousPage={previousPage}
+      fullWidth={frontMatter.fullWidth}
+    >
       {children}
     </DocPage>
   )

develop-docs/sdk/telemetry/logs.mdx

@@ -299,6 +299,8 @@ If the log was paramaterized the SDK should attach the following
 }
 ```
 
+If there are no `sentry.message.parameter.X` attributes included in the log, then the SDK MUST NOT attach a `sentry.message.template` attribute. This is important because it reduces duplicate content in the log and makes PII processing in Sentry much easier as only we don't have to duplicate processing between the log message and the `sentry.message.template` attribute.
+
 #### SDK Integration Attributes
 
 If a log is generated by an SDK integration, the SDK should also set the `sentry.origin` attribute, as per the [Trace Origin](/sdk/telemetry/traces/trace-origin/) documentation. It is assumed that logs without a `sentry.origin` attribute are manually created by the user.

develop-docs/self-hosted/index.mdx

@@ -31,10 +31,10 @@ We require at least **Docker 19.03.6** and **Docker Compose 2.32.2**. It is reco
 
 These are the minimum requirements:
 - 4 CPU Cores
-- 16 GB RAM
+- 16 GB RAM + 16 GB swap
 - 20 GB Free Disk Space
 
-We also recommend using a swapfile whenever applicable.
+We recommend using 32 GB RAM, but it works with 16 GB RAM + 16 GB swap as well. You will not notice a downside if your 16 GB swap is on a high speed disk.
 
 Depending on your traffic volume, you may want to increase your system specification to handle increased load. Although most of the times, this is not the case for self-hosted Sentry, since no matter how small or big the traffic is, you will most likely hover around the same used resources.
 

docs/organization/integrations/cloud-monitoring/aws-lambda/index.mdx

@@ -4,13 +4,6 @@ sidebar_order: 1
 description: "Learn more about Sentry's AWS Lambda integration and how you can automatically instrument your Node or Python Lambda functions with Sentry without changing your code."
 ---
 
-<Alert>
-
-This method of setting up Sentry in your Lambda functions only works if your Lambda functions are run in Node CommonJS (`require` syntax) or in Python.
-For all other setups, check out these docs for [Node](/platforms/javascript/guides/aws-lambda/) or [Python](/platforms/python/integrations/aws-lambda/) instead.
-
-</Alert>
-
 Connect Sentry to your AWS account to automatically add Sentry error and performance monitoring to your Node/Python Lambda functions.
 
 ## Install
@@ -111,7 +104,7 @@ If you're using [Serverless framework](https://www.serverless.com/), note that t
 
 You can confirm that the output works by inputting `aws lambda get-function-configuration --function-name <yourFunctionName>`. However, when you perform a subsequent `sls deploy` the environment variables aren't maintained even though it looks like the reference to the layer is retained.
 
-You can set the layer definition and environment variables in `serverless.yml` as a workaround, but you'll have to do two things manually: maintain the latest layer version and add the reference to the SDK layer for every function you want "Sentrified".
+You can set the layer definition and environment variables in `serverless.yml` as a workaround, but you'll have to do two things manually: maintain the latest layer version and add the reference to the SDK layer for every function you want to add Sentry to.
 
 **Serverless Framework Using Node:**
 
@@ -123,12 +116,12 @@ provider:
   region: <AWS_REGION>
   environment:
     SENTRY_TRACES_SAMPLE_RATE: "1.0"
-    SENTRY_DSN: "<SENTRY_DSN>"
-    NODE_OPTIONS: "-r @sentry/aws-serverless/dist/awslambda-auto"
+    SENTRY_DSN: "___PUBLIC_DSN___"
+    NODE_OPTIONS: "--import @sentry/aws-serverless/awslambda-auto"
 
 custom:
   layers:
-    - arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryNodeServerlessSDK:26
+    - arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryNodeServerlessSDKv10:15
 #    - arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryNodeServerlessSDK:latest
 
 functions:
@@ -147,11 +140,11 @@ provider:
   region: <AWS_REGION>
   environment:
     SENTRY_TRACES_SAMPLE_RATE: "1.0"
-    SENTRY_DSN: "<SENTRY_DSN>"
+    SENTRY_DSN: "___PUBLIC_DSN___"
 
 custom:
   layers:
-    - arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryPythonServerlessSDK:6
+    - arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryPythonServerlessSDK:167
 #    - arn:aws:lambda:${self:provider.region:943013980633:layer:SentryPythonServerlessSDK:latest
 
 functions:

docs/organization/integrations/data-visualization/amazon-sqs/index.mdx

@@ -5,7 +5,7 @@ description: "Learn about Sentry's Amazon SQS integration, which allows you to f
 ---
 <Alert>
 
-Amazon SQS integration is deprecated and is not availble to be installed on new projects.
+Amazon SQS integration is deprecated and is not available to be installed on new projects.
 
 </Alert>
 Amazon SQS is useful for a more in-depth analysis of exceptions, making it quick and easy to pipe exceptions back into your own systems. Or, use it to empower other teams, such as a Business Intelligence function.

docs/organization/integrations/data-visualization/segment/index.mdx

@@ -5,7 +5,7 @@ description: "Learn about Sentry's Segment integration, which allows you to coll
 ---
 <Alert>
 
-Segment integration is deprecated and is not availble to be installed on new projects.
+Segment integration is deprecated and is not available to be installed on new projects.
 
 </Alert>
 

docs/organization/integrations/data-visualization/splunk/index.mdx

@@ -5,7 +5,7 @@ description: "Learn more about Sentry's Splunk integration, which allows you to
 ---
 <Alert>
 
-Splunk integration is deprecated and is not availble to be installed on new projects.
+Splunk integration is deprecated and is not available to be installed on new projects.
 
 </Alert>
 

docs/organization/integrations/integration-platform/webhooks.mdx

@@ -42,6 +42,7 @@ This header lets you know which resource from the list below triggered an action
 - `metric_alert`
 - `error`
 - `comment`
+- `seer`
 
 ### `Sentry-Hook-Signature`
 
@@ -146,6 +147,8 @@ Webhooks should respond within 1 second. Otherwise, the response is considered a
 
 - [Errors](/organization/integrations/integration-platform/webhooks/errors/)
 
+- [Seer](/organization/integrations/integration-platform/webhooks/seer/)
+
 ## Developing and Testing Webhooks
 
 If you’d like to test webhook configuration and look at payloads before starting development, an HTTP catch-all service that provides a designated URL where you can receive HTTP payloads and inspect the JSON event payload can come in handy. After you’ve reviewed the relevant event payloads, you can begin development.