Actionable insights to resolve Astro performance bottlenecks and errors. Improve your monitoring workflow with a full view of releases so you can mark Astro errors as resolved and prioritize live issues.
Just run this commmand to install and register Sentry's Astro integraion.
npx astro add @sentry/astro
And add your DSN and project config to your astro.config.mjs
file:
import { defineConfig } from "astro/config"; import sentry from "@sentry/astro"; export default defineConfig({ integrations: [ sentry({ dsn: "__DSN__", sourceMapsUploadOptions: { project: "your-project-slug", authToken: process.env.SENTRY_AUTH_TOKEN, }, tracesSampleRate: 1.0, }), ], });
Check our documentation for the latest instructions.
See all platformsSentry works with OpenTelemetry to provide a simple configuration process, and rich distributed tracing context across all the libraries and frameworks used in your application. Regardless of your chosen tech stack.
Quickly identify performance issues and view full end-to-end distributed trace to see the exact poor-performing API call and surface any related Astro errors. Improve Astro performance with max efficiency, not max effort.
See the error and Astro stack trace previously only visible in your user’s debug console. Apply source maps automatically to convert minified, compiled, or transpiled code back to its original form. Keep your Astro source maps private by uploading them directly to Sentry.
See what the app was doing when the Astro error occurred: user interactions, AJAX requests, console log messages, and more. Learn in which version a bug first appeared, merge duplicates, and know if things regress in a future release
Record environment and usage details so you can recreate bugs down to the browser version, OS, and query parameters specific to your app.
Sentry’s tag distribution graph makes it easy to isolate and prioritize any Astro error by seeing how often it occurs in context.
Find answers to key questions: How actionable is this error? Was the bug browser or OS specific?
Even a one-second delay in loading results in a 7% reduction in conversions.
Forty percent of customers abandon a website that takes longer than three seconds to load.
The average cost of downtime is $5,600 per minute — or $300,000 per hour.
Sentry supports every major frontend language, framework, and library. You can browse each of them here.
You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our pricing page.
Sentry doesn’t impact a web site’s performance.
If you look at the configuration options for when you initialize Sentry in your code, you’ll see there’s nothing regarding minimizing its impact on your app’s performance. This is because our team of SDK engineers already developed Sentry with this in mind.
Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.
Global handlers have almost no impact as well, as they are native APIs provided by the browsers.
Here’s a quick look at how Sentry handles your personal information (PII).
×We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
Am I included?We may disclose your PII to the following type of recipients:
You may have the following rights related to your PII:
If you have any questions or concerns about your privacy at Sentry, please email us at compliance@sentry.io.
If you are a California resident, see our Supplemental notice.