Deno

We've released v8 of the JavaScript SDKs. If you're using version 7.x, we recommend upgrading to the latest version. Check out the Migration docs to learn how to make the switch.

Don't have a Sentry account? Sign up for Sentry for free, then return to this page.

Configuration should happen as early as possible in your application's lifecycle.

In addition to capturing errors, you can monitor interactions between multiple services or applications by enabling tracing.

Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.

Copied
import * as Sentry from "https://deno.land/x/sentry/index.mjs";

Sentry.init({
  dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",

  // Set tracesSampleRate to 1.0 to capture 100%
  // of transactions for performance monitoring.
  // We recommend adjusting this value in production
  tracesSampleRate: 1.0,
});

To ensure the SDK can send events, you should enable network access for your ingestion domain:

Copied
deno run --allow-net=o0.ingest.sentry.io index.ts

To ensure the SDK can include your source code in stack traces, you should enable read access for your source files:

Copied
deno run --allow-read=./src index.ts

This snippet includes an intentional error, so you can test that everything is working as soon as you set it up.

Verify your setup by adding the following snippet anywhere in your code and running it:

Copied
setTimeout(() => {
  throw new Error();
});

Learn more about manually capturing an error or message in our Usage documentation.

To view and resolve the recorded error, log into sentry.io and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").