@sentry/opentelemetry
Advanced tools
Changelog
8.38.0
knex
integration (#13526)tedious
integration (#13486)debug_meta
with ANR events (#14203)Work in this release was contributed by @grahamhency, @Zen-cronic, @gilisho and @phuctm97. Thank you for your contributions!
Changelog
8.37.0
piniaIntegration
(#14138)The Nuxt SDK now allows you to track Pinia state for captured errors. To enable the Pinia plugin, add the piniaIntegration
to your client config:
// sentry.client.config.ts
import { usePinia } from '#imports';
Sentry.init({
integrations: [
Sentry.piniaIntegration(usePinia(), {
/* optional Pinia plugin options */
}),
],
});
The Sentry Metrics beta has ended in favour of revisiting metrics in another form at a later date.
This new approach will include different APIs, making the current metrics API unnecessary. This release deprecates the metrics API with the plan to remove in the next SDK major version. If you currently use the metrics API in your code, you can safely continue to do so but sent data will no longer be processed by Sentry.
Learn more about the end of the Metrics beta.
http.response_delivery_type
attribute to resource spans (#14056)skipBrowserExtensionCheck
escape hatch option (#14147)asyncFunctionReExports
to define re-exported server functions (#14104)piniaIntegration
(#14138)maybeInstrument
(#14140)modulesIntegration
does not crash esm apps (#14169)Work in this release was contributed by @rexxars. Thank you for your contribution!
Changelog
8.36.0
With this release, the Sentry Next.js, and Cloudflare SDKs will now capture performance data based on OpenTelemetry. Some exceptions apply in cases where Next.js captures inaccurate data itself.
NOTE: You may experience minor differences in transaction names in Sentry.
Most importantly transactions for serverside pages router invocations will now be named GET /[param]/my/route
instead of /[param]/my/route
.
This means that those transactions are now better aligned with the OpenTelemetry semantic conventions.
child_process
and worker_thread
(#13896).mjs
entry files in rollup (#14060)onError
callback (#14002)Changelog
8.35.0
This release marks the beta release of the @sentry/nuxt
Sentry SDK. For details on how to use it, check out the
Sentry Nuxt SDK README. Please reach out on
GitHub if you have any feedback or concerns.
import()
(#13945)It is no longer required to add a Node --import
flag. Please update your start command to avoid initializing Sentry
twice (BREAKING CHANGE). The SDK will now apply modifications during the build of your application to allow for
patching of libraries during runtime. If run into issues with this change, you can disable this behavior in your
nuxt.config.ts
and use the --import
flag instead:
sentry: {
dynamicImportForServerEntry: false;
}
We now require you to explicitly enable sourcemaps for the clientside so that Sentry can un-minify your errors. We made this change so source maps aren't accidentally leaked to the public. Enable source maps on the client as follows:
export default defineNuxtConfig({
sourcemap: {
client: true,
},
});
responseHook
with waitUntil
(#13986)Support for Pinia is added in this release for @sentry/vue
. To capture Pinia state data,
add createSentryPiniaPlugin()
to your Pinia store:
import { createPinia } from 'pinia';
import { createSentryPiniaPlugin } from '@sentry/vue';
const pinia = createPinia();
pinia.use(createSentryPiniaPlugin());
This change introduces a new SentryHttpInstrumentation
to handle non-span related HTTP instrumentation, allowing it to
run side-by-side with OTel's HttpInstrumentation
. This improves support for custom OTel setups and avoids conflicts
with Sentry's instrumentation. Additionally, the spans: false
option is reintroduced for httpIntegration
to disable
span emission while still allowing custom HttpInstrumentation
instances (httpIntegration({ spans: false })
).
This change adds a new option trackFetchStreamPerformance
to the browser tracing integration. Only when set to true
,
Sentry will instrument streams via fetch.
suppressTracing
API (#13875)@opentelemetry/instrumentation-express
to 0.43.0
(#13948)@opentelemetry/instrumentation-fastify
to 0.40.0
(#13983)init
is correct in meta frameworks
(#13938).set
the sentry-trace
header instead of .append
ing in fetch instrumentation
(#13907)ignoreOutgoingRequests
of httpIntegration
applies to breadcrumbs
(#13970)Work in this release was contributed by @ZakrepaShe and @zhiyan114. Thank you for your contributions!