Sentry

You can connect Sentry and Jam in order to view your Sentry logs right from Jam. This gives you easy visibility of the bug from the frontend (captured with Jam) to all the other services across your infrastructure that the bug traces across (captured with Sentry).

The goal: make it much faster for engineers to find the issue causing any reported bug by pairing Jam + Sentry together.

How to get started and connect Jam & Sentry

1. Jam will detect if Sentry is installed on a website, and show a Sentry tab if Sentry is detected. Click on that tab to be guided through authenticating with Sentry. If Sentry is not installed on the website, have no fear, there is another way to connect! Go to your Jam team workspace account settings, click on "Connected Apps", and connect to Sentry from there.
2. Integrating with Sentry is a team plan only feature in Jam. If you are connecting to Sentry from a Jam that is not in a team, Jam will prompt you to create a team and move the Jam to your newly created team. Once your Jam is in a team workspace, you will be prompted to connect Sentry. Click on the button and go through the Sentry OAuth flow to connect Jam to Sentry.
3. Done! Now you can view Sentry events right from Jam.

Now you will be able to see Sentry events from the same timestamp of the Jam right in the Jam.

If you are on a Sentry business plan, you will be able to see events across all your Sentry projects. If you are on a lower Sentry tier, you will only be able to choose 1 project to view logs from at a time.

You can scope the logs by timestamp, and filter by specific keywords to find relevant Sentry events. Click on any Sentry event listed in Jam to open up that log in Sentry.

How are Sentry logs chosen to be surfaced in Jam?

Jam's goal is to show engineers relevant logs from Sentry right in Jam.

Jam filters Sentry logs displayed in Jam by timestamp. By default, Jam will display Sentry logs from the 5 minutes before and after the Jam was created.

By default, Jam will filter the logs you see by the detected environment field sent to Sentry from the frontend. For example, if the client web application sends events to Sentry with the environment field "staging", then Sentry logs shown in the Jam will be default scoped to show "environment:staging".

Our goal is to over time, be able to show you only the most relevant Sentry logs so that we help you quickly and easily trace bugs across your infrastructure. We'd love to hear how you've instrumented Sentry such that we can find the proper Sentry logs for any bug. Please reach out with any feedback to [e-mail].

Which plan includes the Sentry integration?

Integrating with Sentry is a team plan only feature in Jam. Connecting with Sentry will require you to create a team and move the Jam to that newly created team. You can learn more about our pricing here: jam.dev/pricing.