Sentry

Sentry watches your app once it's in real users' hands. When something throws, it captures the crash with a full stack trace, the device and OS, and the steps that led there, then groups similar errors together so you fix the cause once. It also tracks performance, so you can see which screens and calls are slow. In an app you build with Appsanic, you use it to know about crashes before your users tell you about them.

What you get by connecting it

Connect Sentry once and the agent wires it in for you:

• Initialises Sentry at the app root so errors anywhere in the app are captured from the first frame.
• Tags every event with the user ID and the release, so you can tell which build broke and for whom.
• Uploads source maps at build time (when you've supplied an auth token), so a crash report maps back to your readable source rather than minified gibberish.

You describe what you want monitored in plain English. The agent handles the wiring.

Connecting it

You need your DSN, and optionally an auth token for source map uploads.

1. In Sentry, open Project settings then Client Keys (DSN) and copy the DSN. It's a URL that's public by design and safe to embed.
2. For readable stack traces, create an auth token in Sentry (it starts with sntrys_) with permission to upload source maps. This step is optional; skip it and crashes still report, just against minified code.
3. Paste the DSN (and token, if you have one) into Dashboard then Connectors then Sentry. Connect once and every project in your account can use it. Connecting requires a paid plan.

Saved secrets show as dots, never the value. The page has a Test connection control to re-check the credentials against Sentry, and a Disconnect control to remove them.

Keys and security

Sentry is a just connect connector. The DSN is publishable by design, so the agent embeds it directly in the app where Sentry needs it. There's no server-side relay and no account access toggle. The auth token is used only at build time to upload source maps and is never bundled into the app people download.

Like every managed connector, anything you save is encrypted at rest with AES-256-GCM. The browser only ever sees that a secret exists, the AI never sees a decrypted value, and the agent never asks you for a key in chat.

Useful links

• Sentry documentation: https://docs.sentry.io
• Appsanic guide: Error Monitoring

Next

Read Error Monitoring for how crash reporting and alerting fit together across the apps you build.