JavaScript Error and Performance Monitoring

Resolve JavaScript errors with max efficiency, not max effort. Get actionable insights to resolve JavaScript performance issues with the ability to track, debug, and resolve JavaScript errors across platforms.

Getting Started is Simple

Grab the Sentry JavaScript SDK:

HTML
<script src="https://browser.sentry-cdn.com/latest/bundle.min.js"></script>

Configure your DSN:

JavaScript
Sentry.init({
  dsn: 'https://<key>@sentry.io/<project>',
  integrations: [Sentry.browserTracingIntegration()],
  tracesSampleRate: 1.0,
  tracePropagationTargets: ['localhost', /^\/https:\/\/yourserver\.io\/api/],
});

Grab the Sentry React SDK:

Bash
npm install @sentry/react

Create an instrument.js file and add the Sentry initialization code. This file must be imported before any other imports in your application entry point:

JSX
import * as Sentry from "@sentry/react";

Sentry.init({
  dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
  integrations: [
    Sentry.browserTracingIntegration(),
    Sentry.replayIntegration(),
  ],
  tracesSampleRate: 1.0,
  tracePropagationTargets: [/^\//, /^https:\/\/yourserver\.io\/api/],
  replaysSessionSampleRate: 0.1,
  replaysOnErrorSampleRate: 1.0,
});

Include the Sentry initialization file as the first import statement:

JSX
import "./instrument";
import App from "./App";
import { createRoot } from "react-dom/client";
import * as Sentry from "@sentry/react";

const container = document.getElementById("app");
const root = createRoot(container, {
  onUncaughtError: Sentry.reactErrorHandler(),
  onCaughtError: Sentry.reactErrorHandler(),
  onRecoverableError: Sentry.reactErrorHandler(),
});
root.render(<App />);

Signup and install Sentry with just one line of code:

Bash
npx @sentry/wizard@latest -i nextjs

Grab the Sentry Vue SDK:

Bash
npm install @sentry/vue

Configure your DSN:

JavaScript
import { createApp } from "vue";
import * as Sentry from "@sentry/vue";

const app = createApp({
  // ...
});

Sentry.init({
  app,
  dsn: "https://<key>@sentry.io/<project>",
  integrations: [Sentry.browserTracingIntegration()],

  // We recommend adjusting this value in production, or using tracesSampler
  // for finer control
  tracesSampleRate: 1.0,
  // Set tracePropagationTargets to control for which URLs distributed tracing should be enabled
  tracePropagationTargets: ['localhost', /^https:\/\/yourserver\.io\/api/],
});

app.mount("#app");

Install with one line of code:

Bash
npx @sentry/wizard@latest -i angular

Just run this command to sign up for and install Sentry:

Bash
npx @sentry/wizard@latest -i remix

To use the SDK, initialize Sentry in your Svelte entry point main.js before you bootstrap your Svelte app:

JavaScript
// main.js / main.ts

import App from "./App.svelte";

import * as Sentry from "@sentry/svelte";

// Initialize the Sentry SDK here
Sentry.init({
  dsn: "__DSN__",
  release: "my-project-name@2.3.12",

  integrations: [Sentry.browserTracingIntegration()],

  // We recommend adjusting this value in production
  tracesSampleRate: 1.0,

  // Set tracePropagationTargets to control for which URLs distributed tracing should be enabled
  tracePropagationTargets: ['localhost', /^https:\/\/yourserver\.io\/api/],
});

// Then bootstrap your Svelte app
const app = new App({
  target: document.getElementById("app"),
});

export default app;

Install with one line of code:

Bash
npm install @sentry/electron --save

Configure your SDK:

JavaScript
import * as Sentry from "@sentry/electron";
Sentry.init({ dsn: "https://<key>@sentry.io/<project>" });

Grab the Sentry Ember SDK:

HTML
<script src="https://browser.sentry-cdn.com/11.0.0/bundle.min.js"></script>

Configure your DSN:

JavaScript
Sentry.init({
  dsn: 'https://<key>@sentry.io/<project>',
  integrations: [new Sentry.Integrations.Ember()]
});

Just run this command to install and register Sentry's Astro integration:

Bash
npx astro add @sentry/astro

Just run this command to install and register Sentry's Nuxt integration:

Bash
npx @sentry/wizard@latest -i nuxt

Check our documentation for the latest instructions.

See All Platforms

How to install the JavaScript SDK

JavaScript Performance Monitoring

Quickly identify JavaScript performance issues before they become downtime. View the entire end-to-end distributed trace to see the exact, poor-performing API call and surface any related errors.
See a Sample Transaction

Complete Stack Traces, Even When Minified

See the error and JavaScript stack trace previously only visible in your user's debug console. Apply source maps automatically to convert minified, compiled, or transpiled code back to its original form. Keep your JavaScript source maps private by uploading them directly to Sentry.
See a Sample Stack Trace

Issues, replayed

Get to the root cause of an error or latency issue faster with context like DOM events, console logs, and network calls within one visual replay on your web application.
Check out Session Replay

Fill In the Blanks

See what the app was doing when the JavaScript error occurred: user interactions with component names, AJAX requests, console log messages and more. When frontend errors happen, Sentry can prompt users for feedback so you can compare their experiences to the data.
Check out Breadcrumbs

Understand Where Tests Could Prevent Regressions

Quickly isolate Code Coverage for JavaScript bugs to see where testing could help fix the bug before release with our Codecov integration.
Learn More About Codecov by Sentry
Sentry Logs showing structured log output alongside errors and traces

Your Logs, Next to the Error

Send structured logs from the browser and your Node services to the same place as your errors and traces. When a JavaScript error fires, the log lines around it are already there — no tab-switching to a separate logging tool to reconstruct what happened.

Learn more about Logs in Sentry.

Explore Logs

"We were able to catch errors with Sentry before customers could report them or before they hit our support queue."

Ian White
Founder/CEO at ChartHop
ChartHop

See The Full Picture Of Any Exception

Record environment and usage details so you can recreate bugs down to the browser version, OS, and query parameters specific to the session.

Sentry's tag distribution graph also makes it easy to isolate and prioritize any JavaScript error by seeing how often it occurs in context.

Answer the most important questions: Was the bug browser or OS specific? Firefox or Safari?

You can't afford to put JavaScript monitoring on the backburner.

Even a one-second delay in loading results in a 7% reduction in conversions.

Forty percent of customers abandon a website that takes longer than three seconds to load.

The average cost of downtime is $5,600 per minute — or $300,000 per hour.

FAQs

Traditional logging provides you with a trail of events. Some of those events are errors, but many times they're simply informational. Sentry is fundamentally different because we focus on exceptions, or in other words, we capture application crashes. We discuss in more detail here and on our blog.

Sentry supports every major frontend language, framework, and library. You can browse each of them here.

You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our pricing page.

Sentry doesn't impact a web site's performance.

If you look at the configuration options for when you initialize Sentry in your code, you'll see there's nothing regarding minimizing its impact on your app's performance. This is because our team of SDK engineers already developed Sentry with this in mind.

Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.

Global handlers have almost no impact as well, as they are native APIs provided by the browsers.

Yes. Sentry Logs lets you send, view, and query structured logs from your application alongside your errors and traces. Because logs sit next to the error and the trace that produced them, you get the granular context — retries, API failures, internal state — that spans and stack traces alone can miss, without switching tools.

Learn more about Logs in Sentry.

Seer is Sentry's AI debugging agent. It reads the full context Sentry already has — the error, its stack trace, the surrounding trace, logs, and profiles — to find the root cause of an issue and propose a fix. Seer can open a pull request with that fix, hand the work to an external coding agent, or review your PRs before they ship.

Learn more about Seer and Autofix.

Supporting Resources

Frontend Monitoring Documentation

Eventbrite Customer Story

Replace console.log with structured, trace-connected logging using LogTape and Sentry

Send Vercel AI SDK telemetry to Sentry via OpenTelemetry

A better experience for your users. An easier life for your developers.