Sentry-Compatible Error Tracking Platforms | Telebugs

Monitor issues throughout your whole stack

Use Telebugs with Sentry SDKs across JavaScript, Python, Ruby, PHP, Go, mobile, server, and client apps. Self-hosted error tracking for your stack.

Telebugs accepts error events from Sentry SDKs, so most platform support starts with a familiar pattern: keep the SDK, point the DSN at your Telebugs instance, then send a real test exception.

Use this page to choose the right route: a dedicated framework guide, a general language page, a migration checklist, or the broader Sentry SDK-compatible validation path.

For exact SDK installation options, check the Sentry platform documentation and the Telebugs supported platforms appendix. For the compatibility model, read Sentry SDK compatible error tracking.

Choose your path

Situation Start here Validate before rollout
Your framework has a dedicated Telebugs guide Use the matching guide below for setup notes, feature context, and buyer fit. Send a staging event, check grouping, notifications, release data, and source maps or worker context.
You use Python or Go broadly Use the general Python or Go page, then map it to your framework. Test web requests and background work separately if your app has both.
You are switching from Sentry Use the Sentry migration guide and stack migration examples. Keep the old DSN available until Telebugs receives useful production errors.
Your runtime has no dedicated guide yet Use the broader SDK matrix below and the Sentry SDK compatibility page. Confirm the SDK sends standard error events with the context your team needs.

Dedicated guides

These pages have dedicated Telebugs content. Use them when the stack matches your app, then pair the guide with the broader validation checklist below.

Stack Guide First validation target
React React error tracking Browser error, release value, route breadcrumbs, and source map resolution.
Next.js Next.js error tracking Client error, server error, API route error, release, and source maps.
Vue Vue error tracking Component error, route breadcrumbs, release, and source map behavior.
Rails Rails error tracking Controller exception, job error, tags, user context, and release.
Laravel Laravel error tracking HTTP exception, queue job, environment, request context, and notifications.
Django Django error tracking View exception, Celery task, request data, tags, and environment.
Python Python error tracking Framework integration, worker process, logging context, and release value.
Go Go error tracking HTTP handler error, middleware behavior, tags, release, and notification routing.

Broader SDK coverage

Telebugs is not limited to the dedicated guides above. If your runtime has a Sentry SDK that sends standard error events, it belongs on the evaluation list. Use this matrix as a starting point, then send a real test exception before moving production traffic.

Stack Common apps Telebugs path
Angular Browser apps, dashboards, admin panels. Use the Sentry JavaScript Angular SDK path, then verify browser context, releases, and source maps.
Svelte / SvelteKit Client apps, server-rendered routes, forms, and APIs. Use the JavaScript SDK path and verify client and server events separately.
Astro Content sites, hybrid apps, server islands, and integrations. Use the matching JavaScript/Node SDK setup for the runtime you deploy.
Swift / iOS / macOS Native iOS and macOS apps. Use the Sentry Apple SDK and test release, environment, and user context fields.
.NET Services, workers, scheduled jobs, and desktop apps. Use the Sentry .NET SDK path and validate exception type, stack frames, tags, and release.
ASP.NET Core APIs, web apps, middleware-heavy services, and background workers. Validate request context, route data, user context, and worker errors separately.
Spring Boot / Java JVM web services, APIs, queues, and scheduled jobs. Use the Sentry Java/Spring integration and confirm tags, breadcrumbs, and stack frames.
Android / Kotlin Native Android apps and mobile SDK workflows. Validate release names, device context, handled errors, and production privacy filtering.

Validation before production

Platform support is only useful when the reports are useful to your team. Before moving a production service, validate the event shape, routing, and operating expectations.

  • Send a controlled staging error from every runtime that matters: web request, browser bundle, worker, queue, scheduled job, or mobile app.
  • Confirm grouping, stack traces, release, environment, tags, user context, breadcrumbs, and request data.
  • For JavaScript apps, confirm releases and source maps resolve readable frames.
  • Trigger one notification through the intended production channel.
  • Review sensitive data before broad rollout, especially request fields, user context, extras, and breadcrumbs.
  • If you are migrating from Sentry, keep the previous DSN available until rollback is no longer needed.
  • If self-hosting is the main question, use the installation readiness checklist.