feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
feat(nextjs/vercel-edge/cloudflare): Switch to OTEL for performance monitoring (#13889)
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.
Other Changes
deps: Bump bundler plugins and CLI to 2.22.6 and 2.37.0 respectively (#14050)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.44.0 to 0.45.0 (#14099)
feat(deps): bump @opentelemetry/instrumentation-connect from 0.39.0 to 0.40.0 (#14101)
feat(deps): bump @opentelemetry/instrumentation-express from 0.43.0 to 0.44.0 (#14102)
feat(deps): bump @opentelemetry/instrumentation-fs from 0.15.0 to 0.16.0 (#14098)
feat(deps): bump @opentelemetry/instrumentation-kafkajs from 0.3.0 to 0.4.0 (#14100)
feat(nextjs): Add method and url to route handler request data (#14084)
feat(node): Add breadcrumbs for child_process and worker_thread (#13896)
fix(core): Ensure standalone spans are not sent if SDK is disabled (#14088)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore condition...
_Description has been truncated_
Bumps the sentry group with 5 updates:
8.35.0
8.36.0
8.35.0
8.36.0
8.35.0
8.36.0
8.35.0
8.36.0
8.35.0
8.36.0
Updates
@sentry/browser
from 8.35.0 to 8.36.0Release notes
Sourced from
@sentry/browser
's releases.... (truncated)
Changelog
Sourced from
@sentry/browser
's changelog.Commits
13e6c8e
release: 8.36.0a566681
Merge pull request #14136 from getsentry/prepare-release/8.36.009c8577
meta(changelog): Update changelog for 8.36.0b6dbde8
Merge pull request #14135 from getsentry/master472c228
ref(nuxt): Revert Sentry Pinia plugin (#14134)a9cedf9
Merge pull request #14120 from getsentry/prepare-release/8.36.0c98377b
fix(aws-serverless): Remove possible prototype pollution source (#14110)a091bdd
feat(replay): ExposerecordingMode
in public API (#14085)8d9322c
meta(changelog): Update changelog for 8.36.006ef628
feat(nextjs): Add method and url to route handler request data (#14084)Updates
@sentry/nestjs
from 8.35.0 to 8.36.0Release notes
Sourced from
@sentry/nestjs
's releases.... (truncated)
Changelog
Sourced from
@sentry/nestjs
's changelog.Commits
13e6c8e
release: 8.36.0a566681
Merge pull request #14136 from getsentry/prepare-release/8.36.009c8577
meta(changelog): Update changelog for 8.36.0b6dbde8
Merge pull request #14135 from getsentry/master472c228
ref(nuxt): Revert Sentry Pinia plugin (#14134)a9cedf9
Merge pull request #14120 from getsentry/prepare-release/8.36.0c98377b
fix(aws-serverless): Remove possible prototype pollution source (#14110)a091bdd
feat(replay): ExposerecordingMode
in public API (#14085)8d9322c
meta(changelog): Update changelog for 8.36.006ef628
feat(nextjs): Add method and url to route handler request data (#14084)Updates
@sentry/nextjs
from 8.35.0 to 8.36.0Release notes
Sourced from
@sentry/nextjs
's releases.... (truncated)
Changelog
Sourced from
@sentry/nextjs
's changelog.Commits
13e6c8e
release: 8.36.0a566681
Merge pull request #14136 from getsentry/prepare-release/8.36.009c8577
meta(changelog): Update changelog for 8.36.0b6dbde8
Merge pull request #14135 from getsentry/master472c228
ref(nuxt): Revert Sentry Pinia plugin (#14134)a9cedf9
Merge pull request #14120 from getsentry/prepare-release/8.36.0c98377b
fix(aws-serverless): Remove possible prototype pollution source (#14110)a091bdd
feat(replay): ExposerecordingMode
in public API (#14085)8d9322c
meta(changelog): Update changelog for 8.36.006ef628
feat(nextjs): Add method and url to route handler request data (#14084)Updates
@sentry/node
from 8.35.0 to 8.36.0Release notes
Sourced from
@sentry/node
's releases.... (truncated)
Changelog
Sourced from
@sentry/node
's changelog.Commits
13e6c8e
release: 8.36.0a566681
Merge pull request #14136 from getsentry/prepare-release/8.36.009c8577
meta(changelog): Update changelog for 8.36.0b6dbde8
Merge pull request #14135 from getsentry/master472c228
ref(nuxt): Revert Sentry Pinia plugin (#14134)a9cedf9
Merge pull request #14120 from getsentry/prepare-release/8.36.0c98377b
fix(aws-serverless): Remove possible prototype pollution source (#14110)a091bdd
feat(replay): ExposerecordingMode
in public API (#14085)8d9322c
meta(changelog): Update changelog for 8.36.006ef628
feat(nextjs): Add method and url to route handler request data (#14084)Updates
@sentry/opentelemetry
from 8.35.0 to 8.36.0Release notes
Sourced from
@sentry/opentelemetry
's releases.... (truncated)
Changelog
Sourced from
@sentry/opentelemetry
's changelog.Commits
13e6c8e
release: 8.36.0a566681
Merge pull request #14136 from getsentry/prepare-release/8.36.009c8577
meta(changelog): Update changelog for 8.36.0b6dbde8
Merge pull request #14135 from getsentry/master472c228
ref(nuxt): Revert Sentry Pinia plugin (#14134)a9cedf9
Merge pull request #14120 from getsentry/prepare-release/8.36.0c98377b
fix(aws-serverless): Remove possible prototype pollution source (#14110)a091bdd
feat(replay): ExposerecordingMode
in public API (#14085)8d9322c
meta(changelog): Update changelog for 8.36.006ef628
feat(nextjs): Add method and url to route handler request data (#14084)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show