← All platforms

Cloudflare error tracking

Your Worker runs at the edge. Its error reports can live on your server. Connect the Sentry Cloudflare SDK to Telebugs and keep both choices.

~/hoofnotes  npm install @sentry/cloudflare
~/hoofnotes  nvim wrangler.jsonc src/index.ts
{
"name": "hoofnotes",
"main": "src/index.ts",
"compatibility_date": "2026-09-04",
"compatibility_flags": ["nodejs_compat"]
}
import * as Sentry from "@sentry/cloudflare";
import { worker } from "./hoofnotes";
export default Sentry.withSentry(
() => ({
// Copy the complete Telebugs DSN, key and path included.
dsn: "YOUR_TELEBUGS_DSN",
}),
worker,
);
~/hoofnotes  npm run dev

Hang on, I already use Sentry

Keep @sentry/cloudflare and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.

Does my Worker need to move?

No. Your code stays on Cloudflare. The SDK wraps your Worker’s handlers and sends captured exceptions to your reachable Telebugs endpoint.

And Cloudflare Pages Functions?

The same SDK offers Pages middleware. It can send function errors to Telebugs too; plain browser errors use the JavaScript SDK.