@sentry-internal/replay
Advanced tools
Changelog
8.33.0
headers()
, params
, searchParams
)
(#13828)Adds support for new dynamic Next.js APIs.
lru-memoizer
instrumentation
(#13796)Adds integration for lru-memoizer using @opentelemetry/instrumentation-lru-memoizer.
unstable_sentryBundlerPluginOptions
to module options
(#13811)Allows passing other options from the bundler plugins (vite and rollup) to Nuxt module options.
wrap()
only returns functions
(#13838)getTraceData
and getTraceMetaTags
if SDK is disabled
(#13760)Work in this release was contributed by @joshuajaco. Thank you for your contribution!
Changelog
8.32.0
Moves the description of navigation related browser spans into the op, e.g. browser - cache -> browser.cache and sets the description to the performanceEntry objects' names (in this context it is the URL of the page).
feat(node): Add amqplibIntegration (#13714)
feat(nestjs): Add SentryGlobalGenericFilter
and allow specifying application ref in global filter
(#13673)
Adds a SentryGlobalGenericFilter
that filters both graphql and http exceptions depending on the context.
Sets log levels in breadcrumbs for 5xx to error and 4xx to warning.
sampled
flag from dynamic sampling context in Tracing without Performance mode
(#13753)Work in this release was contributed by @Zen-cronic and @Sjoertjuh. Thank you for your contributions!
Changelog
8.31.0
dataloader
integration (#13664)This release adds a new integration for the dataloader
package. The Node
SDK (and all SDKs that depend on it) will now automatically instrument dataloader
instances. You can also add it
manually:
Sentry.init({
integrations: [Sentry.dataloaderIntegration()],
});
activationStart
timestamp to pageload span (#13658)deleteSourcemapsAfterUpload
(#13610)http.server.prefetch
op (#13600)disableInstrumentationWarnings
option (#13693)experimental_basicServerTracing
option to Nuxt module (#13643)onError
callback + other small improvements to debugging (#13721)consoleSandbox
(#13690)lazyLoadIntegration
script parent element lookup (#13717)SentryTraced
functions (#13684)Propagator.inject
(#13381)Work in this release was contributed by @KyGuy2002, @artzhookov, and @julianCast. Thank you for your contributions!
Changelog
8.30.0
kafkajs
integration (#13528)This release adds a new integration that instruments kafkajs
library with spans and traces. This integration is
automatically enabled by default, but can be included with the Sentry.kafkaIntegration()
import.
Sentry.init({
integrations: [Sentry.kafkaIntegration()],
});
@opentelemetry/instrumentation-undici
for fetch tracing (#13485)trackComponents
list matches components with or without <>
(#13543)Work in this release was contributed by @Zen-cronic and @odanado. Thank you for your contributions!
Changelog
8.29.0
This release marks the beta releases of the @sentry/solid
and @sentry/solidstart
Sentry SDKs. For details on how to
use them, check out the
Sentry Solid SDK README and the
Sentry SolidStart SDK README
respectively. Please reach out on GitHub if you have
any feedback or concerns.
Adds the SDK option to only wrap ES modules with import-in-the-middle
that specifically need to be instrumented.
import * as Sentry from '@sentry/node';
Sentry.init({
dsn: '__PUBLIC_DSN__',
registerEsmLoaderHooks: { onlyIncludeInstrumentedModules: true },
});
All internal OpenTelemetry instrumentation was updated to their latest version. This adds support for Mongoose v7 and v8 and fixes various bugs related to ESM mode.
generic-pool
integration (#13465)browserTracingIntegration
by default (#13561)sentrySolidStartVite
plugin to simplify source maps upload (#13493)context.waitUntil
call in request handler (#13549)generic-pool
span origins with underscores (#13579)Work in this release was contributed by @Zen-cronic. Thank you for your contribution!
Changelog
8.28.0
This release contains the beta version of @sentry/nestjs
! For details on how to use it, check out the
README. Any feedback/bug reports
are greatly appreciated, please reach out on GitHub.
This release fixes a bug in the @sentry/browser
package and all SDKs depending on this package (e.g. @sentry/react
or @sentry/nextjs
) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDK
previously incorrectly processed the original values as they were reported from the browser. When updating your SDK to
this version, you might experience an increase in LCP, FCP and FP values, which potentially leads to a decrease in your
performance score in the Web Vitals Insights module in Sentry. This is because the previously reported values were
smaller than the actually measured values. We apologize for the inconvenience!
SentryGlobalGraphQLFilter
(#13545)bundleSizeOptimizations
to build options (#13323)captureRequestError
(#13550)@Injectable
(#13544)Work in this release was contributed by @leopoldkristjansson, @mhuggins and @filips123. Thank you for your contributions!
Changelog
8.27.0
fix(nestjs): Exception filters in main app module are not being executed (#13278)
With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule
to your
application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter
to
your main module providers or decorate the catch()
method in your existing global exception filters with the newly
released @WithSentry()
decorator. See the docs for
more details.
Deno.permissions.querySync
(#13378)Work in this release was contributed by @charpeni. Thank you for your contribution!
Changelog
8.26.0
feat(node): Add fsInstrumentation
(#13291)
This release adds fsIntegration
, an integration that instruments the fs
API to the Sentry Node SDK. The
integration creates spans with naming patterns of fs.readFile
, fs.unlink
, and so on.
This integration is not enabled by default and needs to be registered in your Sentry.init
call. You can configure
via options whether to include path arguments or error messages as span attributes when an fs call fails:
Sentry.init({
integrations: [
Sentry.fsIntegration({
recordFilePaths: true,
recordErrorMessagesAsSpanAttributes: true,
}),
],
});
WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of file I/O, like for example when running a framework dev server, including this integration can massively slow down your application.
feat(browser): Add spotlightBrowser integration (#13263)
feat(browser): Allow sentry in safari extension background page (#13209)
feat(browser): Send CLS as standalone span (experimental) (#13056)
feat(core): Add OpenTelemetry-specific getTraceData
implementation (#13281)
feat(nextjs): Always add browserTracingIntegration
(#13324)
feat(nextjs): Always transmit trace data to the client (#13337)
feat(nextjs): export SentryBuildOptions (#13296)
feat(nextjs): Update experimental_captureRequestError
to reflect RequestInfo.path
change in Next.js canary
(#13344)
feat(nuxt): Always add tracing meta tags (#13273)
feat(nuxt): Set transaction name for server error (#13292)
feat(replay): Add a replay-specific logger (#13256)
feat(sveltekit): Add bundle size optimizations to plugin options (#13318)
feat(sveltekit): Always add browserTracingIntegration (#13322)
feat(tracing): Make long animation frames opt-out (#13255)
fix(astro): Correctly extract request data (#13315)
fix(astro): Only track access request headers in dynamic page requests (#13306)
fix(nuxt): Add import line for disabled autoImport
(#13342)
fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)
fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)
fix(remix): Ensure origin
is correctly set for remix server spans (#13305)
Work in this release was contributed by @MonstraG, @undead-voron and @Zen-cronic. Thank you for your contributions!