Skip to content

Conversation

@chargome
Copy link
Member

We want to gain better insights how much usage we get from the SDK on Cloudflare.

When Next.js apps are deployed to Cloudflare Workers via OpenNext, the Sentry SDK now correctly reports cloudflare as the runtime instead of node or vercel-edge.

e2e tests still failing cry

@github-actions
Copy link
Contributor

github-actions bot commented Jan 29, 2026

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario Requests/s % of Baseline Prev. Requests/s Change %
GET Baseline 8,672 - 8,842 -2%
GET With Sentry 1,724 20% 1,673 +3%
GET With Sentry (error only) 6,021 69% 5,638 +7%
POST Baseline 1,193 - 1,077 +11%
POST With Sentry 594 50% 527 +13%
POST With Sentry (error only) 1,052 88% 1,016 +4%
MYSQL Baseline 3,228 - 3,199 +1%
MYSQL With Sentry 491 15% 394 +25%
MYSQL With Sentry (error only) 2,648 82% 2,617 +1%

View base workflow run

@chargome chargome self-assigned this Jan 30, 2026
chargome and others added 2 commits January 30, 2026 16:33
Server-side transactions are not reliably available on Cloudflare Workers,
so the tests now verify the cloudflare runtime and SDK metadata using error
events instead.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@github-actions
Copy link
Contributor

github-actions bot commented Jan 30, 2026

Codecov Results 📊


Generated by Codecov Action

@chargome chargome marked this pull request as ready for review January 30, 2026 16:15
@chargome chargome requested a review from logaretm January 30, 2026 16:23
@chargome chargome merged commit 5bd3a79 into develop Jan 30, 2026
217 checks passed
@chargome chargome deleted the cg-next-cf-runtime branch January 30, 2026 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants