> ## Documentation Index
> Fetch the complete documentation index at: https://jam.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Sentry
> See Sentry backend errors and logs alongside your Jam captures. Trace bugs from the frontend all the way through your stack.
Connect Jam to Sentry to see backend errors and service logs right alongside your frontend captures. When a bug is reported with Jam, you can immediately see the Sentry events from the same timeframe, giving engineers a direct path from the symptom to the root cause across your full infrastructure.
The Sentry integration is available on the Team plan only. See [jam.dev/pricing](https://jam.dev/pricing) for details.
## How the integration works
When Sentry is connected, Jam displays Sentry events from the 5 minutes before and after the Jam was created. Logs are filtered by the environment field sent from your frontend to Sentry. For example, if your client app sends events with `environment: staging`, Jam will scope the displayed Sentry logs to `environment:staging` by default.
You can also:
* Filter logs by timestamp range
* Search for specific keywords to find relevant Sentry events
* Click any Sentry event listed in Jam to open it directly in Sentry
If you're on a Sentry business plan, you can view events across all your Sentry projects. On lower Sentry tiers, you can view one project at a time.
## Connect Jam to Sentry
When you open a Jam on a website where Sentry is detected, a Sentry tab appears automatically. Click it to begin the authentication flow.
Click the connect button and authorize Jam through the Sentry OAuth flow.
Once connected, Sentry events from the same timeframe as the Jam appear directly inside the Jam view.
If Sentry is not installed on the website you're capturing, you can still connect from the Jam dashboard. Go to [**Settings → Integrations**](https://jam.dev/s/settings/integrations) and connect Sentry from there.