Merge branch 'master' into remove-hardcoded-domain

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.

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/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.

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

@@ -0,0 +1,275 @@
+---
+title: Seer
+sidebar_order: 7
+description: "Learn more about Sentry's integration platform Seer webhooks for Issue Fix analysis notifications."
+---
+
+Sentry integrations that have subscribed to Seer webhooks can receive notifications about the Seer [Issue Fix](/product/ai-in-sentry/seer/issue-fix/) process. These webhooks allow you to track the progress of automated root cause analysis, solution generation, and code fixes.
+
+## Sentry-Hook-Resource Header
+
+`'Sentry-Hook-Resource': 'seer'`
+
+## Webhook Types
+
+Seer webhooks support seven different event types that track the complete lifecycle of AI-powered issue resolution:
+
+### Root Cause Analysis
+- `seer.root_cause_started` - Triggered when root cause analysis begins
+- `seer.root_cause_completed` - Triggered when root cause analysis completes with results
+
+### Solution Generation
+- `seer.solution_started` - Triggered when solution generation begins
+- `seer.solution_completed` - Triggered when a solution has been generated
+
+### Code Generation
+- `seer.coding_started` - Triggered when code generation/fixing begins
+- `seer.coding_completed` - Triggered when code changes are ready
+- `seer.pr_created` - Triggered when pull request(s) are created
+
+## Common Attributes
+
+All Seer webhooks share these common attributes:
+
+### action
+
+- type: string
+- description: The specific Seer event that occurred (e.g., `root_cause_started`, `solution_completed`)
+
+### data['run_id']
+
+- type: integer
+- description: Unique identifier for this Seer analysis run
+
+### data['group_id']
+
+- type: integer
+- description: The Sentry issue ID being analyzed
+
+## Event-Specific Payloads
+
+### Root Cause Started
+
+Minimal payload indicating analysis has begun:
+
+```json
+{
+  "action": "root_cause_started",
+  "actor": {
+    "id": "sentry",
+    "name": "Sentry",
+    "type": "application"
+  },
+  "data": {
+    "run_id": 12345,
+    "group_id": 1170820242
+  },
+  "installation": {
+    "uuid": "a8e5d37a-696c-4c54-adb5-b3f28d64c7de"
+  }
+}
+```
+
+### Root Cause Completed
+
+Includes the identified root cause:
+
+```json
+{
+  "action": "root_cause_completed",
+  "actor": {
+    "id": "sentry",
+    "name": "Sentry",
+    "type": "application"
+  },
+  "data": {
+    "run_id": 12345,
+    "group_id": 1170820242,
+    "root_cause": {
+      "description": "Woah wow there's a bug here.",
+      "steps": [
+        {
+          "title": "User navigates to the dashboard page, initiating page load.",
+          "code_snippet_and_analysis": "The user's browser sends a GET request to `/dashboard`. This is the entry point for the issue.",
+          "timeline_item_type": "human_action",
+          "relevant_code_file": {
+            "file_path": "N/A",
+            "repo_name": "N/A"
+          },
+          "is_most_important_event": false
+        },
+        {
+          "title": "Next.js server renders the /dashboard route.",
+          "code_snippet_and_analysis": "The Next.js server processes the request and hits the bug",
+          "timeline_item_type": "internal_code",
+          "relevant_code_file": {
+            "file_path": "src/app/page.ts",
+            "repo_name": "owner/repo"
+          },
+          "is_most_important_event": true
+        }
+      ]
+    }
+  },
+  "installation": {
+    "uuid": "a8e5d37a-696c-4c54-adb5-b3f28d64c7de"
+  }
+}
+```
+
+### Solution Started
+
+Minimal payload indicating solution generation has begun:
+
+```json
+{
+  "action": "solution_started",
+  "actor": {
+    "id": "sentry",
+    "name": "Sentry",
+    "type": "application"
+  },
+  "data": {
+    "run_id": 12345,
+    "group_id": 1170820242
+  },
+  "installation": {
+    "uuid": "a8e5d37a-696c-4c54-adb5-b3f28d64c7de"
+  }
+}
+```
+
+### Solution Completed
+
+Includes the generated solution details:
+
+```json
+{
+  "action": "solution_completed",
+  "actor": {
+    "id": "sentry",
+    "name": "Sentry",
+    "type": "application"
+  },
+  "data": {
+    "run_id": 12345,
+    "group_id": 1170820242,
+    "solution": {
+      "description": "Definitely need to fix this.",
+      "steps": [
+        {
+          "title": "Go fix it",
+        },
+        {
+          "title": "Then go fix this other thing.",
+        },
+      ],
+      
+    }
+  },
+  "installation": {
+    "uuid": "a8e5d37a-696c-4c54-adb5-b3f28d64c7de"
+  }
+}
+```
+
+### Coding Started
+
+Minimal payload indicating code generation has begun:
+
+```json
+{
+  "action": "coding_started",
+  "actor": {
+    "id": "sentry",
+    "name": "Sentry",
+    "type": "application"
+  },
+  "data": {
+    "run_id": 12345,
+    "group_id": 1170820242
+  },
+  "installation": {
+    "uuid": "a8e5d37a-696c-4c54-adb5-b3f28d64c7de"
+  }
+}
+```
+
+### Coding Completed
+
+Includes details about the code changes made:
+
+```json
+{
+  "action": "coding_completed",
+  "actor": {
+    "id": "sentry",
+    "name": "Sentry",
+    "type": "application"
+  },
+  "data": {
+    "run_id": 12345,
+    "group_id": 1170820242,
+    "changes": [
+      {
+        "repo_name": "my-app",
+        "repo_external_id": "12345",
+        "title": "fix: Initialize undefined variable",
+        "description": "This change initializes the 'blooopy' variable before use to prevent ReferenceError",
+        "diff": "<the diff as a string>",
+        "branch_name": "seer/fix-this-thing",
+      }
+    ]
+  },
+  "installation": {
+    "uuid": "a8e5d37a-696c-4c54-adb5-b3f28d64c7de"
+  }
+}
+```
+
+### PR Created
+
+Includes pull request details, there may be more than one pull request if there are multiple repos:
+
+```json
+{
+  "action": "pr_created",
+  "actor": {
+    "id": "sentry",
+    "name": "Sentry",
+    "type": "application"
+  },
+  "data": {
+    "run_id": 12345,
+    "group_id": 1170820242,
+    "pull_requests": [
+      {
+        "pull_request": {
+          "pr_number": 123,
+          "pr_url": "https://github.com/owner/repo/pull/123",
+          "pr_id": 456789
+        },
+        "repo_name": "my-app",
+        "provider": "github"
+      }
+    ]
+  },
+  "installation": {
+    "uuid": "a8e5d37a-696c-4c54-adb5-b3f28d64c7de"
+  }
+}
+```
+
+## Use Cases
+
+Seer webhooks enable you to:
+
+1. **Track Progress**: Monitor the status of Seer Issue Fix in real-time
+2. **Build Notifications**: Send custom notifications when fixes are ready
+3. **Audit Trail**: Maintain a log of all Seer fixes for your issues
+4. **Custom Integrations**: Build custom tools that react to Seer's analysis results
+
+## Best Practices
+
+- Store the `run_id` to correlate related webhook events
+- Use the `group_id` to link webhooks back to the original Sentry issue

docs/platforms/android/integrations/timber/index.mdx

@@ -32,7 +32,7 @@ plugins {
 
 Then, initialize the [Android SDK](/platforms/android/#configure).
 
-The Android SDK automatically adds the `SentryTimberIntegration` if the `sentry-android-timber` dependency was found on the classpath. The integration is added with `minEventLevel` set to `ERROR` and `minBreadcrumbLevel` set to `INFO`.
+The Android SDK automatically adds the `SentryTimberIntegration` if the `sentry-android-timber` dependency was found on the classpath. The integration is added with `minEventLevel` set to `ERROR`, `minBreadcrumbLevel` and `minLogsLevel` set to `INFO`.
 
 However, you can still override the default behaviour by adding your own instance of the `SentryTimberIntegration`. For that, refer to the [manual installation](/platforms/android/integrations/timber/#configure) section below.
 

docs/platforms/android/logs/index.mdx

@@ -5,8 +5,6 @@ description: "Structured logs allow you to send, view and query logs sent from y
 sidebar_order: 5755
 ---
 
-<Include name="feature-stage-beta-logs.mdx" />
-
 With Sentry Structured Logs, you can send text-based log information from your applications to Sentry. Once in Sentry, these logs can be viewed alongside relevant errors, searched by text-string, or searched using their individual attributes.
 
 ## Requirements
@@ -28,3 +26,7 @@ With Sentry Structured Logs, you can send text-based log information from your a
 ## Options
 
 <PlatformContent includePath="logs/options" />
+
+## Default Attributes
+
+<PlatformContent includePath="logs/default-attributes" />