Astro monitoring for every page and every SSR request
One integration in astro.config.mjs and your Astro site reports its own failures: SSR render errors captured automatically by middleware, every server request wrapped in an http.server span, and manual capture available right in your frontmatter. Source maps and session replay live on the same platform.
Why Astro sites need real monitoring
Astro's strength — shipping mostly static HTML with islands of interactivity — also makes its failures easy to miss. A data fetch throws in a page's frontmatter, an SSR route starts returning 500s after a deploy, and unless someone is watching the server logs at that exact moment, the first report comes from a user. Static-feeling sites still have dynamic failure modes, and they deserve the same visibility as any app.
Add the official @sentry/astro integration to astro.config.mjs and initialize it with the DSN from AllStak project setup. Use Sentry.captureException for handled errors and the official build tooling for source maps.
Full Astro site monitoring
From a throwing frontmatter fetch to the SSR request that served it, AllStak covers your Astro site across every layer.
Error tracking
Use the official Astro integration for supported SSR error capture, and call Sentry.captureException for handled errors in frontmatter or server code.
SSR request monitoring
Enable only the server-request instrumentation supported by the official Astro integration and AllStak's current compatibility matrix.
Session replay
See what the user actually did before the error — clicks, navigation, and the moment it broke — with privacy masking so sensitive input never leaves the browser.
Source maps
Upload source maps and minified production stack traces resolve to your original code — file, line, and function — so the fix starts immediately.
Breadcrumbs & release context
Errors arrive with breadcrumbs and the release they shipped in — set release in the integration config and every deploy groups its own issues.
Alerts & incidents
Get notified the moment a new error appears or an old one spikes — before the support tickets arrive, not after.
Add AllStak in minutes
Install from npm (requires astro@>=3.5) and add the integration in astro.config.mjs — SSR errors and requests are monitored from there.
npm install @sentry/astro
import { defineConfig } from 'astro/config';
import sentry from '@sentry/astro';
export default defineConfig({
integrations: [
sentry({ dsn: process.env.ALLSTAK_DSN }),
],
});Set ALLSTAK_DSN in the environment, not in source, and keep release metadata stable so errors group per deploy. Validate optional SSR behavior against the compatibility matrix. full setup guide · SDK reference.
What you see in AllStak
Error detail with full context
Open any issue to a readable stack trace (via source maps), the breadcrumbs leading up to it, and the release it shipped in — reproduction without the guesswork.
SSR requests with method, route, and status
Every server request shows up as an http.server span — so a route that started failing or slowing down after a deploy is visible immediately, not after the complaints.
Session replay of the failure
Watch the user's session around the error — what they clicked, where they navigated, and what the page looked like when it broke.
Unified real-time dashboard
Astro errors next to the logs, uptime, and backend errors of the APIs behind your site — one dashboard, in English or Arabic, for the whole team.
Why teams pick AllStak for Astro
- One integration entry in astro.config.mjs — SSR errors and request monitoring with no extra wiring.
- Manual capture works in frontmatter with Sentry.captureException wherever your data loading lives.
- Session replay and source maps turn vague bug reports into watchable, readable evidence.
- All-in-one platform — errors, logs, traces, and uptime with one bill instead of four tools.
- Predictable SAR pricing with a genuine free tier — start without a credit card.
- Data stays in Saudi Arabia, with an English and Arabic dashboard for the whole team.
Astro monitoring FAQ
How do I add error tracking to an Astro site?
Install @sentry/astro and add the official integration to astro.config.mjs with the DSN from AllStak project setup. Capture handled errors with Sentry.captureException.
Does AllStak work with static Astro sites?
Yes — with one distinction. Manual capture via Sentry.captureException works in frontmatter and server code regardless of output mode. Server-side automatic behavior applies only to supported SSR output; static output has no request pipeline to instrument.
Which Astro versions are supported?
The integration requires astro@>=3.5. Add it like any other Astro integration in astro.config.mjs and configure it with environment variables.
Is AllStak free for Astro?
Yes. AllStak has a free tier you can start on without a credit card, and predictable SAR pricing as you grow. The Astro integration itself is free to use.
Is AllStak a Sentry alternative for Astro?
Yes. You get Astro error tracking with source maps, session replay, and SSR request monitoring like Sentry, plus the logs, uptime, and infrastructure monitoring of everything behind your site on the same platform — one SAR bill and data stored in Saudi Arabia instead of a stack of separate tools.
Explore more
Start monitoring your Astro site today
Add the integration, deploy, and watch errors and SSR requests arrive in one dashboard. Start free — no credit card required.