diff --git a/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-agent-help-options.png b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-agent-help-options.png new file mode 100644 index 0000000000000..74d31027099d4 Binary files /dev/null and b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-agent-help-options.png differ diff --git a/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-oauth-consent.png b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-oauth-consent.png new file mode 100644 index 0000000000000..dcc89274a15a0 Binary files /dev/null and b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-oauth-consent.png differ diff --git a/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-run-or-run-always.png b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-run-or-run-always.png new file mode 100644 index 0000000000000..999b2b4acb0c1 Binary files /dev/null and b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-run-or-run-always.png differ diff --git a/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-triage-claim.png b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-triage-claim.png new file mode 100644 index 0000000000000..5d4edb3098eae Binary files /dev/null and b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-triage-claim.png differ diff --git a/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-triage-rule.png b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-triage-rule.png new file mode 100644 index 0000000000000..b86b8a5f1732a Binary files /dev/null and b/docs/organization/integrations/issue-tracking/sentry-linear-agent/img/Linear-triage-rule.png differ diff --git a/docs/organization/integrations/issue-tracking/sentry-linear-agent/index.mdx b/docs/organization/integrations/issue-tracking/sentry-linear-agent/index.mdx index 3fce90deb4494..78874f7653745 100644 --- a/docs/organization/integrations/issue-tracking/sentry-linear-agent/index.mdx +++ b/docs/organization/integrations/issue-tracking/sentry-linear-agent/index.mdx @@ -9,7 +9,7 @@ og_image: /og-images/organization-integrations-issue-tracking-sentry-linear-agen -**Sentry Agent for Linear** is in its beta phase. It is currently only available for US-based Sentry.io organizations. Changes to the UX and the agent functionality should be expected. +**Sentry Agent for Linear** is in its beta phase. Changes to the UX and the agent functionality should be expected. @@ -24,7 +24,6 @@ This integration highly benefits from having [automation configured within Seer] Sentry owner, manager, or admin permissions are required to install this integration. Linear **won't** work with self-hosted Sentry. - Navigate to **Settings > Integrations > Linear (Sentry Agent)**, accept and install. @@ -42,31 +41,87 @@ When the issue is delegated to the agent, the agent will automatically check for For comment based interactions, the integration accepts natural language. We attempt to parse the intent of the question and trigger the appropriate response. If it fails, we'll prompt the help command that will guide you through options. -Currently the integration allows the user to run the following actions: +Most actions are available via interactive buttons or natural language. Currently, the integration allows the user to run the following actions: - Issue Fix - Runs a Seer Issue Fix for the application. - Status - Updates the status of the issue. - Help - Displays the help command that will guide you through options. +- Enable/Disable automatic Seer runs - Toggle whether Seer automatically runs (without confirmation) when issues are assigned in Linear. +- Enable/Disable Seer PRs - Allow Seer to open pull requests automatically when fixes are ready. + +## Automation & Configuration + +When an issue is assigned to the Sentry Agent in Linear, the user will be prompted to link their account with Sentry. This creates the relationship between your Linear user and your Sentry user, and exposes the projects and Sentry resources the user has access to. + +The OAuth consent screen shows what orgnaization is connecting to Linear as well as gives options that can be enabled to customize the Sentry Agent in Linear's behavior. + +
+ +![OAuth consent screen](./img/Linear-oauth-consent.png) + +
+ +These options can also be managed within the agent interface after the account is linked through the `help` command and leveraging the select menu at the bottom. + +
+ +![Help command](./img/Linear-agent-help-options.png) + +
+ +These options can also be enabled interactively during agent sessions. These options present themselves in the following ways: + +- Via buttons after an issue is assigned: + - `Yes, run Seer RCA` runs Seer Root Cause Analysis (RCA) for the current issue + - `Yes, and run automatically in the future` enables automatic runs in the future for this workspace and starts Seer RCA for the current issue +- Natural language controls: + - "enable automatic seer runs", "disable automatic seer runs" + - "enable Seer PRs", "disable Seer PRs" ## Assigning Sentry Agent to an Issue 1. Navigate to an issue within Linear and select "Assign" from the dropdown menu in the right sidebar. +
+ ![Select Sentry Agent for Linear](./img/Linear-Agent-Delegation.png) +
+ 2. Select "Sentry" from the dropdown menu. 3. The task will be moved into in-progress and the Sentry agent session will be created. If it's your first time using the Agent, you'll be prompted to authenticate. Use the "Link" button to link your Linear user to your Sentry user. ![Link Sentry Agent for Linear](./img/Linear-Linking-Auth.png) -4. Once linked, you'll be asked if you want to run a Seer Issue Fix for the application. You can answer "Yes", or ask for "Help" to see more options. +4. If auto-run is disabled, you'll see a prompt with buttons: + + - `Yes, run Seer RCA` + - `Yes, and run automatically in the future` +
+ ![Enable automatic Seer runs](./img/Linear-run-or-run-always.png) +
+ +5. If auto-run is enabled, the Agent will start Seer automatically and confirm it's running. Use "status" to check progress or view results. If an analysis already exists, the Agent will post the latest status or Sentry issue details. + +
+ + ![Seer RCA in Linear](./img/Linear-Sentry-RCA-2.png) + +
+ + +### Triage Rules + +The Sentry Agent supports Linear's triage rules allowing you to tag issues with a custom label in Linear, and have it execute the Sentry Agent. Examples are below. + +#### Triage Configuration - ![Run Seer in Linear](./img/Linear-Help.png) +![Triage Configuration](./img/Linear-triage-rule.png) -5. If you answer "Yes", the Agent will run a Seer Issue Fix for the application. **Note**: You may need to prompt it for "Status" to see the results. +#### Triage Action - ![RCA from Sentry Seer in Linear](./img/Linear-Sentry-RCA-2.png) +![Triage Action](./img/Linear-triage-claim.png) ## Uninstalling the Integration diff --git a/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx index 1418e777f7d9d..2ec1faeafad99 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx @@ -11,7 +11,7 @@ In this guide you will learn how to set up the `@sentry/aws-serverless` SDK for We recommend starting the SDK automatically via environment variables so that you only have to make minimal code changes to your lambda function. If you need more control over the SDK setup, you can also [initialize the SDK in in code](#alternative-initialize-the-sdk-in-code). -However, you need to modify your code and deploy the Sentry dependencies alongside your function code. If you're looking for the most simple way to set up Sentry, you might want to use the [Lambda Layer](./layer__v9.x.mdx) instead. +However, you need to modify your code and deploy the Sentry dependencies alongside your function code. If you're looking for the most simple way to set up Sentry, you might want to use the [Lambda Layer](layer__v9.x) instead. ## 1. Prerequisites diff --git a/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx index 27303bf92530b..f780f981b686f 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/index__v9.x.mdx @@ -18,11 +18,11 @@ Note that TypeScript can also be configured to output ESM, in which case you sho ### My Lambda function uses `require` -If you are using `require()` in your function, follow the CommonJS instructions. Choose between [using our Lambda Layer (recommended)](./install/layer__v9.x.mdx) or [installing the Sentry AWS NPM package](./install/npm__v9.x.mdx). +If you are using `require()` in your function, follow the CommonJS instructions. Choose between [using our Lambda Layer (recommended)](layer__v9.x) or [installing the Sentry AWS NPM package](npm__v9.x). ### My Lambda function uses `import` -If you're using `import` syntax in your function and you're _not_ transpiling the code to CommonJS, follow the [ESM instructions](./install/esm-npm__v9.x.mdx). +If you're using `import` syntax in your function and you're _not_ transpiling the code to CommonJS, follow the [ESM instructions](esm-npm__v9.x). ### Can I use the Lambda layer for ESM functions? diff --git a/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx index ab5246299ff56..bc05c9c02cffa 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx @@ -8,13 +8,13 @@ noindex: true og_image: /og-images/platforms-javascript-guides-aws-lambda-install-layer__v8.x.png --- -The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/Lambda/latest/dg/configuration-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](../install/npm.mdx). +The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/Lambda/latest/dg/configuration-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](npm). If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code. To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it. -This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../install/npm.mdx). +This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](npm). diff --git a/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx index 56b72c91a802c..dca4db876c33f 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/layer__v9.x.mdx @@ -7,13 +7,13 @@ sidebar_order: 1 og_image: /og-images/platforms-javascript-guides-aws-lambda-install-layer__v9.x.png --- -The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/adding-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](./npm__v9.x.mdx). +The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/adding-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](npm__v9.x). If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code. To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it. -This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../npm__v9.x.mdx). +This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](esm-npm__v9.x). diff --git a/docs/platforms/javascript/guides/aws-lambda/install/npm__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/npm__v9.x.mdx index ecbc8c578957c..d312d476110ee 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/npm__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/npm__v9.x.mdx @@ -8,13 +8,13 @@ Based on whether your Lambda function runs in CommonJS or ESM, you need to follo ## My Lambda function is written in TypeScript -If you're using TypeScript, your lambda function is likely transpiled to CommonJS before running it. In this case, follow the [CommonJS instructions](./cjs-npm__v9.x.mdx). -Note that TypeScript can also be configured to output ESM, in which case you should follow the [ESM instructions](./esm-npm__v9.x.mdx). +If you're using TypeScript, your lambda function is likely transpiled to CommonJS before running it. In this case, follow the [CommonJS instructions](cjs-npm__v9.x). +Note that TypeScript can also be configured to output ESM, in which case you should follow the [ESM instructions](esm-npm__v9.x). ## My Lambda function uses `require` -If you are using `require()` in your function, follow the [CommonJS instructions](./cjs-npm__v9.x.mdx). +If you are using `require()` in your function, follow the [CommonJS instructions](cjs-npm__v9.x). ## My Lambda function uses `import` -If you're using `import` syntax in your function and you're _not_ transpiling the code to CommonJS, follow the [ESM instructions](./esm-npm__v9.x.mdx). +If you're using `import` syntax in your function and you're _not_ transpiling the code to CommonJS, follow the [ESM instructions](esm-npm__v9.x). diff --git a/redirects.js b/redirects.js index 72f223f97f5ef..cf03facf04e43 100644 --- a/redirects.js +++ b/redirects.js @@ -790,6 +790,10 @@ const userDocsRedirects = [ source: '/platforms/javascript/guides/:guide/configuration/integrations/trycatch/', destination: '/platforms/javascript/configuration/integrations/browserapierrors/', }, + { + source: '/platforms/javascript/configuration/integrations/supabase/', + destination: '/platforms/javascript/guides/node/configuration/integrations/supabase/', + }, { source: '/api/releases/post-organization-release-files/', destination: '/api/releases/update-an-organization-release-file/',