You can send new exceptions from an application to Epure without replacing its Sentry SDK: create an Epure project, change the SDK’s DSN on every instrumented runtime, and verify that events appear in the intended project. The “10 min” in the original title is not a reliable completion estimate; the work can take longer when several app surfaces, sourcemap uploads, or alert integrations need changes.
What changes—and what stays
- Keep the Sentry SDK. Epure says to retain the official SDK for your runtime; it does not provide a separate
@epure/*client. Examples include@sentry/node,@sentry/nextjs,sentry-sdk, andsentry-go. - Change the DSN. Use the DSN for the Epure project in place of the Sentry ingest DSN. Update it everywhere events are sent, including browser, server, worker, and edge deployments where applicable.
- Keep useful release and environment values. Existing values can continue to support filtering, regression tracking, and sourcemap matching.
- Turn off unsupported product lines. Epure says performance or transaction events, session replay, and profiling are discarded. Set their corresponding sample rates to zero. For JavaScript SDK 8.x, set
enableTracing: falsetoo if that option is present in your configuration.
Migration steps
-
Create the destination project
Run Epure, create a workspace and project, and copy that project’s DSN. The project DSN is the destination for the SDK events you want to move.
As an Amazon Associate I earn from qualifying purchases.
-
Update every application surface
Replace the old DSN with the Epure DSN wherever the SDK is configured. Check deployment secrets and environment variables as well as source configuration; a browser-facing change alone will not redirect server-side events.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Disable discarded telemetry
Set tracing, replay, and profiling sample rates to zero in the relevant SDK configurations. In JavaScript SDK 8.x, also disable tracing with
enableTracing: falsewhen that setting is available. This avoids continuing to configure product data Epure does not retain.#1 Best Overall
-
Retarget JavaScript sourcemap uploads, if used
Change the upload destination used by
@sentry/clior your Vite upload tooling to the Epure host. Keep the uploaded artifact’s release value aligned with the release sent by the application. Epure says other languages remain raw frames, so this sourcemap procedure applies to JavaScript and TypeScript rather than being a general stack-symbolication migration. -
Send and verify a test exception
Trigger an exception through the application SDK and confirm that the ingest request returns HTTP 202. Epure’s quickstart notes that this response can arrive before the issue row appears, so then check the correct project for the issue rather than treating the response as proof that it is already visible.
-
Recreate integrations, then retire the old DSN
Recreate the alerts and webhooks you still need in Epure; Sentry alert rules do not import. If you want to check production behavior before finishing the cutover, use a dual-send or soak period where appropriate, then remove the previous DSN after verification.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
What does not migrate automatically
- Historical issues: Epure does not import past Sentry issues. Events begin appearing in Epure after the DSN change; retain access to Sentry if old issue history must remain available.
- Issue grouping: Epure uses its own fingerprinting behavior, so an issue may group differently after the move.
- Alerts and webhooks: Recreate the rules and endpoints needed for the new project rather than expecting Sentry configurations to carry over.
- Tracing, replay, and profiling data: These are discarded on ingest, not transferred as retained Epure data.
Check these failure points if events are missing
- No issue appears after a successful ingest response: Allow for the issue row to appear after the HTTP 202 response, then check that you are viewing the intended Epure project and environment.
- Browser events arrive but server errors do not: Check server-side deployment variables and secrets separately from browser-facing configuration; each runtime needs the destination DSN.
- Events appear in an unexpected place or the feed looks empty: Confirm the project DSN and environment filter. A request can be accepted while the project or filter being viewed is wrong.
- JavaScript stacks are minified: Verify that CI uploads sourcemaps to the Epure host and that the upload release string matches the release value reported by the application.
Decide whether the move fits your setup
This migration is most straightforward when the requirement is exception tracking and the team can accept a fresh issue history in Epure. Before switching, weigh the following:
- Required capabilities: If the workflow depends on APM or tracing, replay, or profiling, Epure’s documented handling of those event types is a material limitation.
- Historical continuity: If old Sentry issues must remain queryable, plan to preserve access to that history because it will not be imported.
- Operations: Epure’s welcome documentation describes a self-hosted setup with two Compose containers and PostgreSQL 16. The practical operational difference from a Sentry deployment depends on the existing installation and workload; those figures alone do not establish a universal cost or savings.
- Migration risk: Count the SDK configurations, deployment environments, sourcemap pipelines, and alert destinations involved. A dual-send or soak period can help teams validate production behavior before removing the former DSN.
The key cutover is the DSN change, but a complete migration also accounts for telemetry Epure discards, integrations that must be rebuilt, and the historical issues that stay in Sentry.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
