@sentry-internal/replay-canvas

Sentry Session Replay with Canvas

Pre-requisites

Replay with canvas requires Node 14+, and browsers newer than IE11.

Installation

Replay and ReplayCanvas can be imported from @sentry/browser, or a respective SDK package like @sentry/react or @sentry/vue. You don't need to install anything in order to use Session Replay. The minimum version that includes Replay is 7.27.0.

For details on using Replay when using Sentry via the CDN bundles, see CDN bundle.

Setup

To set up the canvas integration, add the following to your Sentry integrations:

Sentry.replayCanvasIntegration(),

Full Example

import * as Sentry from '@sentry/browser';
// or e.g. import * as Sentry from '@sentry/react';

Sentry.init({
  dsn: '__DSN__',

  // This sets the sample rate to be 10%. You may want this to be 100% while
  // in development and sample at a lower rate in production
  replaysSessionSampleRate: 0.1,

  // If the entire session is not sampled, use the below sample rate to sample
  // sessions when an error occurs.
  replaysOnErrorSampleRate: 1.0,

  integrations: [Sentry.replayIntegration(), Sentry.replayCanvasIntegration()],
  // ...
});

Changelog

10.15.0

Important Changes

• feat(cloudflare): Add honoIntegration with error-filtering function (#17743)

  This release adds a honoIntegration to @sentry/cloudflare, which exposes a shouldHandleError function that lets you define which errors in onError should be captured. By default, Sentry captures exceptions with error.status >= 500 || error.status <= 299.

  The integration is added by default, and it's possible to modify this behavior like this:

   integrations: [
     honoIntegration({
      shouldHandleError: (err) => true; // always capture exceptions in onError
     })
   ]
  

• feat(node): Add instrumentation for hono handler (#17428)

This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.

• feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)

• feat(browser): Add setActiveSpanInBrowser to set an active span in the browser (#17714)

This PR adds a feature to the browser SDKs only: Making an inactive span active. We do this to enable use cases where having a span only being active in the callback is not practical.

Other Changes

• fix(browser): Improve handling of 0 and undefined resource timing values (#17751)
• ref(nextjs): Display build compatibility warning for webpack (#17746)

<details> <summary> <strong>Internal Changes</strong> </summary>

• docs: Reword changelog for google gen ai instrumentation (#17753)
• build: Add @typescript-eslint/no-unnecessary-type-assertion rule (#17728)
• build: Update TS target to es2020 everywhere (#17709)
• chore: Add external contributor to CHANGELOG.md (#17745)

</details>

Work in this release was contributed by @Karibash. Thank you for your contribution!