Track errors with Sentry
This example demonstrates how to track errors with Sentry using Trigger.dev.
Overview
Automatically send errors and source maps to your Sentry project from your Trigger.dev tasks. Sending source maps to Sentry allows for more detailed stack traces when errors occur, as Sentry can map the minified code back to the original source code.
Prerequisites
- A Sentry account and project
- A Trigger.dev account and project
Build configuration
To send errors to Sentry when there are errors in your tasks, you’ll need to add this build configuration to your trigger.config.ts
file. This will then run every time you deploy your project.
You will need to set the SENTRY_AUTH_TOKEN
and SENTRY_DSN
environment variables. You can find
the SENTRY_AUTH_TOKEN
in your Sentry dashboard, in settings -> developer settings -> auth tokens
and the SENTRY_DSN
in your Sentry dashboard, in settings -> projects -> your project -> client
keys (DSN). Add these to your .env
file, and in your Trigger.dev
dashboard, under environment variables in your project’s sidebar.
Build extensions allow you to hook into the build system and customize the build process or the resulting bundle and container image (in the case of deploying). You can use pre-built extensions or create your own.
Testing that errors are being sent to Sentry
To test that errors are being sent to Sentry, you need to create a task that will fail.
This task takes no payload, and will throw an error.
After creating the task, deploy your project.
Once deployed, navigate to the test
page in the sidebar of your Trigger.dev dashboard, click on your prod
environment, and select the sentryErrorTest
task.
Run a test task with an empty payload by clicking the Run test
button.
Your run should then fail, and if everything is set up correctly, you will see an error in the Sentry project dashboard shortly after.
Was this page helpful?