Docs / Switch from Sentry

Docs · By hand

Switch from Sentry by changing the DSN

At the end your Sentry SDK sends its errors and captured messages to Vinktar. The rest of your code stays as it is.

Before you start

You need a Vinktar project and an app that reports to Sentry. A Sentry SDK in any language can point its DSN at Vinktar. Its errors and captured messages go through the same pipeline as the Vinktar SDKs.

Errors and captured messages are stored. Transactions, sessions, replays, profiles, attachments and client reports are accepted and dropped, so the SDK logs no failures. If you rely on Sentry for tracing or replay, keep it for those.

Without Sentry.setUser({ id }) a browser error arrives anonymous and joins to no person. Send the same id your analytics uses, and the error and the person are one record.

1. Change the DSN

# was: SENTRY_DSN=https://abc123@o12345.ingest.sentry.io/451
SENTRY_DSN=https://vnk_pk_YOUR_KEY@in.vinktar.com/YOUR_PROJECT_ID

The key is the project's public write key. The finished DSN, with the project id filled in, is on the project's Connect page under Manual, and your agent gets it from get_project_keys.

On Laravel the variable is SENTRY_LARAVEL_DSN: Send Laravel errors with the Sentry SDK. On Symfony it is SENTRY_DSN: Send Symfony errors with the Sentry SDK.

2. Set the user

Sentry.setUser({ id: 'user_123' });   // after sign-in, same id as your analytics
Sentry.setUser(null);                 // on logout

3. Check it worked

Throw an error from your app. It appears on the project's Errors page as an issue. Open it and check the stack, release, environment and user id. The table below records the same checks for each tested SDK.

Tested SDKs

Each row is one real thrown error from an unmodified SDK against this server, checked on the issue and the stored occurrence: the issue exists, stack frames are present, and release, environment, user id and the breadcrumb arrived.

SDKVersionDateIssueStackReleaseEnvironmentUserBreadcrumbsNote
@sentry/node11.4.02026-10-05passpasspasspasspasspass—
@sentry/browser11.4.02026-10-05passpasspasspasspasspassChrome; a throw inside setTimeout is stored unhandled with mechanism "manual".
@sentry/nextjs11.4.02026-10-05passpasspasspasspasspassRoute handler via onRequestError; server frames are minified until maps are uploaded.
sentry-sdk (Python)2.71.02026-10-05passpasspasspasspasspass—
sentry/sentry-laravel4.28.02026-10-05passpasspasspasspasspassArtisan command; the SDK adds its own start and finish breadcrumbs.
sentry/sentry-symfony5.13.02026-10-05passpasspasspasspasspass—

Node, browser, Next.js, Python, Laravel and Symfony work with the DSN change alone. Other Sentry SDKs speak the same envelope protocol and are expected to, but only these six have been run against this server.

Limits and responses

The endpoint accepts Sentry's envelope protocol and the legacy store endpoint. The error rate limit, the monthly error budget and every per-error cap are the ones /v1/errors applies, and an error sent this way counts against the same budget. Over a limit the answer is 429 with Retry-After. The details are section 11 of api.md.

Source maps

Source maps do not travel over the DSN, and an upload made with Sentry's own tooling still goes to Sentry. To read minified browser stacks here, upload the maps with @vinktarhq/cli under the same release name your Sentry SDK reports. A build stamped by Sentry's bundler plugin (//# debugId=) uploads unchanged with npx @vinktarhq/cli sourcemaps upload; the debug ids on the event match the frames to their maps.

Move to the Vinktar SDK

The DSN carries errors only. Product analytics, and errors joined to the same visitor's events without a setUser call, need the Vinktar SDK, which sends both on one key. Your agent can install it.

Next