Astro on Cloudflare

Learn how to instrument your Astro app on Cloudflare Workers and capture your first errors.

You need:

A Sentry account and project
Your application up and running
Astro 6.0.0 or above
@astrojs/cloudflare v13 or above
@sentry/astro v10.40.0 or above
@sentry/cloudflare v10.40.0 or above

If you're using Cloudflare Pages (not Workers), see the section below for setup instructions. We recommend migrating to Cloudflare Workers for better Sentry integration and full feature support.

Using Astro 3-5 with @astrojs/cloudflare v12?

For Astro 3-5 with @astrojs/cloudflare v12, the @sentry/astro integration automatically detects the Cloudflare adapter and wraps your Worker with the @sentry/cloudflare SDK for proper request isolation and async context.

Follow the standard Astro setup without the custom entry point configuration described below. The SDK handles server-side initialization automatically.

Server-side configuration via environment variables only

With Astro 3-5 on Cloudflare, server-side SDK configuration only works via environment variables. The sentry.server.config.(ts|js) file is not supported.

The SDK reads standard Sentry environment variables including SENTRY_DSN, SENTRY_TRACES_SAMPLE_RATE, SENTRY_RELEASE, SENTRY_ENVIRONMENT, and others. See the SDK configuration spec for the full list.

Using Astro on Cloudflare Pages?

For Cloudflare Pages, you need to manually set up the @sentry/cloudflare SDK using the Pages middleware.

Install both SDKs:

Copied

npm install @sentry/astro @sentry/cloudflare

npm install @sentry/astro @sentry/cloudflare

yarn add @sentry/astro @sentry/cloudflare

pnpm add @sentry/astro @sentry/cloudflare

Add the Sentry Astro integration to your astro.config.mjs:

astro.config.mjs

Copied

import { defineConfig } from "astro/config";
import cloudflare from "@astrojs/cloudflare";
import sentry from "@sentry/astro";

export default defineConfig({
  adapter: cloudflare(),
  integrations: [sentry()],
});

import { defineConfig } from "astro/config";
import cloudflare from "@astrojs/cloudflare";
import sentry from "@sentry/astro";

export default defineConfig({
  adapter: cloudflare(),
  integrations: [sentry()],
});

Create a _middleware.js file in your functions directory (Cloudflare Pages middleware). Create the directory in the root of your project if it doesn't already exist, then create the file and import and initialize the Sentry Cloudflare SDK:

functions/_middleware.js

Copied

import * as Sentry from "@sentry/cloudflare";

export const onRequest = [
  // Make sure Sentry is the first middleware
  Sentry.sentryPagesPlugin((context) => ({
    dsn: "___PUBLIC_DSN___",
    dataCollection: {
      // To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
      // https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/options/#dataCollection
      // userInfo: false,
      // httpBodies: [],
    },
    tracesSampleRate: 1.0,
  })),
  // Add more middlewares here
];

import * as Sentry from "@sentry/cloudflare";

export const onRequest = [
  // Make sure Sentry is the first middleware
  Sentry.sentryPagesPlugin((context) => ({
    dsn: "___PUBLIC_DSN___",
    dataCollection: {
      // To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
      // https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/options/#dataCollection
      // userInfo: false,
      // httpBodies: [],
    },
    tracesSampleRate: 1.0,
  })),
  // Add more middlewares here
];

Make sure to configure Cloudflare for Sentry.

Error MonitoringTracingSession ReplayLogsUser Feedback

Want to learn more about these features?

Issues (always enabled): Sentry's core error monitoring product that automatically reports errors, uncaught exceptions, and unhandled rejections. If you have something that looks like an exception, Sentry can capture it.
Tracing: Track software performance while seeing the impact of errors across multiple systems. For example, distributed tracing allows you to follow a request from the frontend to the backend and back.
Session Replay: Get to the root cause of an issue faster by viewing a video-like reproduction of what was happening in the user's browser before, during, and after the problem.
Logs: Centralize and analyze your application logs to correlate them with errors and performance issues. Search, filter, and visualize log data to understand what's happening in your applications.
User Feedback: Collect feedback directly from users when they encounter errors, allowing them to describe what happened and provide context that helps you understand and resolve issues faster.

Install both @sentry/astro and @sentry/cloudflare:

Copied

npm install @sentry/astro @sentry/cloudflare

npm install @sentry/astro @sentry/cloudflare

yarn add @sentry/astro @sentry/cloudflare

pnpm add @sentry/astro @sentry/cloudflare

Since the SDK needs access to the AsyncLocalStorage API, you need to set the nodejs_compat compatibility flag in your wrangler.(jsonc|toml) configuration file:

wrangler.jsonc

Copied

{
  "compatibility_flags": ["nodejs_compat"],
}

{
  "compatibility_flags": ["nodejs_compat"],
}

compatibility_flags = ["nodejs_compat"]

If you don't set the release option manually, the SDK automatically detects it from these sources (in order of priority):

The SENTRY_RELEASE environment variable
The CF_VERSION_METADATA.id binding (if configured)

To enable automatic release detection via Cloudflare's version metadata, add the CF_VERSION_METADATA binding in your wrangler configuration. This provides access to the Cloudflare version metadata.

wrangler.jsonc

Copied

{
  // ...
  "version_metadata": {
    "binding": "CF_VERSION_METADATA",
  },
}

{
  // ...
  "version_metadata": {
    "binding": "CF_VERSION_METADATA",
  },
}

[version_metadata]
binding = "CF_VERSION_METADATA"

Using an SDK version before 10.35.0?

In earlier versions, you need to manually extract CF_VERSION_METADATA.id and pass it as the release option:

Copied

Sentry.withSentry(
  (env) => ({
    dsn: "___PUBLIC_DSN___",
    release: env.CF_VERSION_METADATA?.id,
  }),
  // ...
);

Sentry.withSentry(
  (env) => ({
    dsn: "___PUBLIC_DSN___",
    release: env.CF_VERSION_METADATA?.id,
  }),
  // ...
);

Astro 6 with @astrojs/cloudflare v13+ supports custom entry points directly from wrangler.jsonc. Update your wrangler configuration to point to a custom Sentry entry point:

wrangler.jsonc

Copied

{
  "main": "./sentry.server.config.ts",
  // ... other configuration
}

{
  "main": "./sentry.server.config.ts",
  // ... other configuration
}

Create a sentry.server.config.ts file in the root of your project that wraps the Astro Cloudflare handler with Sentry:

sentry.server.config.ts

Copied

import * as Sentry from "@sentry/cloudflare";
import handler from "@astrojs/cloudflare/entrypoints/server";

export default Sentry.withSentry(
  (env) => ({
    dsn: env.SENTRY_DSN,
    dataCollection: {
      // To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
      // https://docs.sentry.io/platforms/javascript/guides/astro/configuration/options/#dataCollection
      // userInfo: false,
      // httpBodies: [],
    },
    // ___PRODUCT_OPTION_START___ performance
    // Define how likely traces are sampled. Adjust this value in production,
    // or use tracesSampler for greater control.
    tracesSampleRate: 1.0,
    // ___PRODUCT_OPTION_END___ performance
    // ___PRODUCT_OPTION_START___ logs
    // Enable logs to be sent to Sentry
    enableLogs: true,
    // ___PRODUCT_OPTION_END___ logs
  }),
  handler,
);

import * as Sentry from "@sentry/cloudflare";
import handler from "@astrojs/cloudflare/entrypoints/server";

export default Sentry.withSentry(
  (env) => ({
    dsn: env.SENTRY_DSN,
    dataCollection: {
      // To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
      // https://docs.sentry.io/platforms/javascript/guides/astro/configuration/options/#dataCollection
      // userInfo: false,
      // httpBodies: [],
    },
    // ___PRODUCT_OPTION_START___ performance
    // Define how likely traces are sampled. Adjust this value in production,
    // or use tracesSampler for greater control.
    tracesSampleRate: 1.0,
    // ___PRODUCT_OPTION_END___ performance
    // ___PRODUCT_OPTION_START___ logs
    // Enable logs to be sent to Sentry
    enableLogs: true,
    // ___PRODUCT_OPTION_END___ logs
  }),
  handler,
);

Follow Astro's Cloudflare deployment guide if you haven't already. Then add the Sentry integration to your astro.config.mjs alongside the Cloudflare adapter.

astro.config.mjs

Copied

import { defineConfig } from "astro/config";
import cloudflare from "@astrojs/cloudflare";
import sentry from "@sentry/astro";

export default defineConfig({
  adapter: cloudflare(),
  integrations: [sentry()],
});

import { defineConfig } from "astro/config";
import cloudflare from "@astrojs/cloudflare";
import sentry from "@sentry/astro";

export default defineConfig({
  adapter: cloudflare(),
  integrations: [sentry()],
});

Create a sentry.client.config.(ts|js) file in the root of your project. In this file, import and initialize Sentry for the client:

sentry.client.config.(ts|js)

Copied

import * as Sentry from "@sentry/astro";

Sentry.init({
  dsn: "___PUBLIC_DSN___",

  dataCollection: {
    // To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
    // https://docs.sentry.io/platforms/javascript/guides/astro/configuration/options/#dataCollection
    // userInfo: false,
    // httpBodies: [],
  },

  integrations: [
    // ___PRODUCT_OPTION_START___ performance
    Sentry.browserTracingIntegration(),
    // ___PRODUCT_OPTION_END___ performance
    // ___PRODUCT_OPTION_START___ session-replay
    Sentry.replayIntegration(),
    // ___PRODUCT_OPTION_END___ session-replay
    // ___PRODUCT_OPTION_START___ user-feedback
    Sentry.feedbackIntegration({
      // Additional SDK configuration goes in here, for example:
      colorScheme: "system",
    }),
    // ___PRODUCT_OPTION_END___ user-feedback
  ],
  // ___PRODUCT_OPTION_START___ performance

  // Define how likely traces are sampled. Adjust this value in production,
  // or use tracesSampler for greater control.
  tracesSampleRate: 1.0,
  // ___PRODUCT_OPTION_END___ performance
  // ___PRODUCT_OPTION_START___ session-replay

  // This sets the sample rate to be 10%. You may want this to be 100% while
  // in development and sample at a lower rate in production
  replaysSessionSampleRate: 0.1,

  // If the entire session is not sampled, use the below sample rate to sample
  // sessions when an error occurs.
  replaysOnErrorSampleRate: 1.0,
  // ___PRODUCT_OPTION_END___ session-replay
  // ___PRODUCT_OPTION_START___ logs

  // Enable logs to be sent to Sentry
  enableLogs: true,
  // ___PRODUCT_OPTION_END___ logs
});

import * as Sentry from "@sentry/astro";

Sentry.init({
  dsn: "___PUBLIC_DSN___",

  dataCollection: {
    // To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
    // https://docs.sentry.io/platforms/javascript/guides/astro/configuration/options/#dataCollection
    // userInfo: false,
    // httpBodies: [],
  },

  integrations: [
    // ___PRODUCT_OPTION_START___ performance
    Sentry.browserTracingIntegration(),
    // ___PRODUCT_OPTION_END___ performance
    // ___PRODUCT_OPTION_START___ session-replay
    Sentry.replayIntegration(),
    // ___PRODUCT_OPTION_END___ session-replay
    // ___PRODUCT_OPTION_START___ user-feedback
    Sentry.feedbackIntegration({
      // Additional SDK configuration goes in here, for example:
      colorScheme: "system",
    }),
    // ___PRODUCT_OPTION_END___ user-feedback
  ],
  // ___PRODUCT_OPTION_START___ performance

  // Define how likely traces are sampled. Adjust this value in production,
  // or use tracesSampler for greater control.
  tracesSampleRate: 1.0,
  // ___PRODUCT_OPTION_END___ performance
  // ___PRODUCT_OPTION_START___ session-replay

  // This sets the sample rate to be 10%. You may want this to be 100% while
  // in development and sample at a lower rate in production
  replaysSessionSampleRate: 0.1,

  // If the entire session is not sampled, use the below sample rate to sample
  // sessions when an error occurs.
  replaysOnErrorSampleRate: 1.0,
  // ___PRODUCT_OPTION_END___ session-replay
  // ___PRODUCT_OPTION_START___ logs

  // Enable logs to be sent to Sentry
  enableLogs: true,
  // ___PRODUCT_OPTION_END___ logs
});

Server-side Sentry is already configured in your custom entry point file (sentry.server.config.ts) created in the previous step.

To upload source maps for clear error stack traces, add your Sentry auth token, organization, and project slugs in the sentry options inside astro.config.mjs:

astro.config.mjs

Copied

import { defineConfig } from "astro/config";
import cloudflare from "@astrojs/cloudflare";
import sentry from "@sentry/astro";

export default defineConfig({
  adapter: cloudflare(),
  integrations: [
    sentry({
      org: "___ORG_SLUG___",
      project: "___PROJECT_SLUG___",
      // store your auth token in an environment variable
      authToken: process.env.SENTRY_AUTH_TOKEN,
    }),
  ],
});

import { defineConfig } from "astro/config";
import cloudflare from "@astrojs/cloudflare";
import sentry from "@sentry/astro";

export default defineConfig({
  adapter: cloudflare(),
  integrations: [
    sentry({
      org: "___ORG_SLUG___",
      project: "___PROJECT_SLUG___",
      // store your auth token in an environment variable
      authToken: process.env.SENTRY_AUTH_TOKEN,
    }),
  ],
});

To keep your auth token secure, set the SENTRY_AUTH_TOKEN environment variable in your build environment:

.env.sentry-build-plugin

Copied

SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___

SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___

Using environment variables in Vite configs

Vite doesn't automatically load .env files into process.env when evaluating the config file. If you store your auth token in a .env file and want to access it via process.env.SENTRY_AUTH_TOKEN, use Vite's loadEnv helper.

Alternatively, use a .env.sentry-build-plugin file, which the Sentry plugin reads automatically.

vite.config.js

Copied

import { defineConfig, loadEnv } from "vite";

export default defineConfig(({ mode }) => {
  const env = loadEnv(mode, process.cwd(), "");

  return {
    plugins: [
      sentryVitePlugin({
        authToken: env.SENTRY_AUTH_TOKEN,
        // ...
      }),
    ],
  };
});

import { defineConfig, loadEnv } from "vite";

export default defineConfig(({ mode }) => {
  const env = loadEnv(mode, process.cwd(), "");

  return {
    plugins: [
      sentryVitePlugin({
        authToken: env.SENTRY_AUTH_TOKEN,
        // ...
      }),
    ],
  };
});

Let's test your setup and confirm that Sentry is working correctly and sending data to your Sentry project.

Important

Errors triggered from within your browser's developer tools (like the browser console) are sandboxed, so they will not trigger Sentry's error monitoring.

To verify that Sentry captures errors and creates issues in your Sentry project, create a test page, for example, at src/pages/test.astro with two buttons.

test.astro

Copied

<script>
  const buttonOne = document.getElementById("one");
  const buttonTwo = document.getElementById("two");

  buttonOne.addEventListener("click", throwTestError);
  buttonTwo.addEventListener("click", throwApiError);

  function throwTestError() {
    throw new Error("Sentry Example Frontend Error");
  }

  async function throwApiError() {
    await fetch("/api/test-error");
  }
</script>

<button id="one" type="button">Throw a frontend error</button>
<button id="two" type="button">Throw an API error</button>

<script>
  const buttonOne = document.getElementById("one");
  const buttonTwo = document.getElementById("two");

  buttonOne.addEventListener("click", throwTestError);
  buttonTwo.addEventListener("click", throwApiError);

  function throwTestError() {
    throw new Error("Sentry Example Frontend Error");
  }

  async function throwApiError() {
    await fetch("/api/test-error");
  }
</script>

<button id="one" type="button">Throw a frontend error</button>
<button id="two" type="button">Throw an API error</button>

Then also create the route we're calling in our test page, like src/pages/api/test-error.(js|ts):

Next, open your test page in a browser and click the buttons to trigger a frontend error and an error in the API route.

test-error.(js|ts)

Copied

export async function GET() {
  throw new Error("Sentry Example API Route Error");
}

export async function GET() {
  throw new Error("Sentry Example API Route Error");
}

To test tracing, create a custom span to measure the time it takes for the API request to complete:

test.astro

Copied

<script>
  import * as Sentry from "@sentry/astro";

  const button = document.getElementById("one");

  button.addEventListener("click", throwApiError);

  async function throwApiError() {
    await Sentry.startSpan(
      {
        name: "Example Frontend Span",
        op: "test",
      },
      async () => {
        await fetch("/api/test-error");
      },
    );
  }
</script>

<button id="one" type="button">Throw an API error with a trace</button>

<script>
  import * as Sentry from "@sentry/astro";

  const button = document.getElementById("one");

  button.addEventListener("click", throwApiError);

  async function throwApiError() {
    await Sentry.startSpan(
      {
        name: "Example Frontend Span",
        op: "test",
      },
      async () => {
        await fetch("/api/test-error");
      },
    );
  }
</script>

<button id="one" type="button">Throw an API error with a trace</button>

To verify that Sentry catches your logs, add some log statements to your application:

Copied

Sentry.logger.info("User example action completed");

Sentry.logger.warn("Slow operation detected", {
  operation: "data_fetch",
  duration: 3500,
});

Sentry.logger.error("Validation failed", {
  field: "email",
  reason: "Invalid email",
});

Sentry.logger.info("User example action completed");

Sentry.logger.warn("Slow operation detected", {
  operation: "data_fetch",
  duration: 3500,
});

Sentry.logger.error("Validation failed", {
  field: "email",
  reason: "Invalid email",
});

Now, head over to your project on Sentry.io to view the collected data (it takes a couple of moments for the data to appear).

Need help locating the captured errors in your Sentry project?

Open the Issues page and select an error from the issues list to view the full details and context of this error. For more details, see this interactive walkthrough.
Open the Traces page and select a trace to reveal more information about each span, its duration, and any errors. For an interactive UI walkthrough, click here.
Open the Replays page and select an entry from the list to get a detailed view where you can replay the interaction and get more information to help you troubleshoot.
Open the Logs page and filter by service, environment, or search keywords to view log entries from your application. For an interactive UI walkthrough, click here.
Open the User Feedback page and click on individual feedback to see more details all in one view. For more information, click here.

At this point, you should have integrated Sentry into your Astro application and should already be sending data to your Sentry project.

Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are:

Explore practical guides on what to monitor, log, track, and investigate after setup
Continue to customize your configuration
Learn how to manually capture errors
Get familiar with Sentry's product features like tracing, insights, and alerts

Are you having problems setting up the SDK?

Find various topics in Troubleshooting
Get support

Was this helpful?

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").

How to contribute | Edit this page | Create a docs issue | Get support