Added Sentry example

docs/guides/examples/sentry-error-tracking.mdx

@@ -0,0 +1,120 @@
+---
+title: "Track errors with Sentry"
+sidebarTitle: "Sentry error tracking"
+description: "This example demonstrates how to track errors with Sentry using Trigger.dev."
+---
+
+## Overview
+
+Automatically send errors and source maps to your Sentry project from your Trigger.dev tasks. Sending source maps to Sentry allows for more detailed stack traces when errors occur, as Sentry can map the minified code back to the original source code.
+
+## Prerequisites
+
+- A [Sentry](https://sentry.io) account and project
+- A [Trigger.dev](https://trigger.dev) account and project
+
+## Build configuration
+
+To send errors to Sentry when there are errors in your tasks, you'll need to add this build configuration to your `trigger.config.ts` file. This will then run every time you deploy your project.
+
+<Note>
+  You will need to set the `SENTRY_AUTH_TOKEN` and `SENTRY_DSN` environment variables. You can find
+  the `SENTRY_AUTH_TOKEN` in your Sentry dashboard, in settings -> developer settings -> auth tokens
+  and the `SENTRY_DSN` in your Sentry dashboard, in settings -> projects -> your project -> client
+  keys (DSN). Add these to your `.env` file, and in your [Trigger.dev
+  dashboard](https://cloud.trigger.dev), under environment variables in your project's sidebar.
+</Note>
+
+```ts trigger.config.ts
+import { defineConfig } from "@trigger.dev/sdk/v3";
+import { esbuildPlugin } from "@trigger.dev/build/extensions";
+import { sentryEsbuildPlugin } from "@sentry/esbuild-plugin";
+import * as Sentry from "@sentry/node";
+
+export default defineConfig({
+  project: "<project ref>",
+  // Your other config settings...
+  build: {
+    extensions: [
+      esbuildPlugin(
+        sentryEsbuildPlugin({
+          org: "<your-sentry-org>",
+          project: "<your-sentry-project>",
+          // Find this auth token in settings -> developer settings -> auth tokens
+          authToken: process.env.SENTRY_AUTH_TOKEN,
+        }),
+        { placement: "last", target: "deploy" }
+      ),
+    ],
+  },
+  init: async () => {
+    Sentry.init({
+      // The Data Source Name (DSN) is a unique identifier for your Sentry project.
+      dsn: process.env.SENTRY_DSN,
+      // Update this to match the environment you want to track errors for
+      environment: process.env.NODE_ENV === "production" ? "production" : "development",
+    });
+  },
+  onFailure: async (payload, error, { ctx }) => {
+    Sentry.captureException(error, {
+      extra: {
+        payload,
+        ctx,
+      },
+    });
+  },
+});
+```
+
+<Note>
+  [Build extensions](/config/config-file#extensions) allow you to hook into the build system and
+  customize the build process or the resulting bundle and container image (in the case of
+  deploying). You can use pre-built extensions or create your own.
+</Note>
+
+## Testing that errors are being sent to Sentry
+
+To test that errors are being sent to Sentry, you need to create a task that will fail.
+
+This task takes no payload, and will throw an error.
+
+```ts trigger/sentry-error-test.ts
+import { task } from "@trigger.dev/sdk/v3";
+
+export const sentryErrorTest = task({
+  id: "sentry-error-test",
+  retry: {
+    // Only retry once
+    maxAttempts: 1,
+  },
+  run: async () => {
+    const error = new Error("This is a custom error that Sentry will capture");
+    error.cause = { additionalContext: "This is additional context" };
+    throw error;
+  },
+});
+```
+
+After creating the task, deploy your project.
+
+ <CodeGroup>
+
+    ```bash npm
+    npx trigger.dev@latest deploy
+    ```
+
+    ```bash pnpm
+    pnpm dlx trigger.dev@latest deploy
+    ```
+
+    ```bash yarn
+    yarn dlx trigger.dev@latest deploy
+    ```
+
+    </CodeGroup>
+
+Once deployed, navigate to the `test` page in the sidebar of your [Trigger.dev dashboard](https://cloud.trigger.dev), click on your `prod` environment, and select the `sentryErrorTest` task.
+
+Run a test task with an empty payload by clicking the `Run test` button.
+
+Your run should then fail, and if everything is set up correctly, you will see an error in the Sentry project dashboard shortly after.

docs/guides/introduction.mdx

@@ -47,6 +47,7 @@ Tasks you can copy and paste to get started with Trigger.dev. They can all be ex
 | [React to PDF](/guides/examples/react-pdf)                                    | Use `react-pdf` to generate a PDF and save it to Cloudflare R2.                |
 | [Puppeteer](/guides/examples/puppeteer)                                       | Use Puppeteer to generate a PDF or scrape a webpage.                           |
 | [Resend email sequence](/guides/examples/resend-email-sequence)               | Send a sequence of emails over several days using Resend with Trigger.dev.     |
+| [Sentry error tracking](/guides/examples/sentry-error-tracking)               | Automatically send errors to Sentry from your tasks.                           |
 | [Sharp image processing](/guides/examples/sharp-image-processing)             | Use Sharp to process an image and save it to Cloudflare R2.                    |
 | [Supabase database operations](/guides/examples/supabase-database-operations) | Run basic CRUD operations on a table in a Supabase database using Trigger.dev. |
 | [Supabase Storage upload](/guides/examples/supabase-storage-upload)           | Download a video from a URL and upload it to Supabase Storage using S3.        |

docs/mint.json

@@ -311,6 +311,7 @@
         "guides/examples/pdf-to-image",
         "guides/examples/puppeteer",
         "guides/examples/scrape-hacker-news",
+        "guides/examples/sentry-error-tracking",
         "guides/examples/sharp-image-processing",
         "guides/examples/supabase-database-operations",
         "guides/examples/supabase-storage-upload",