migrate_from_sentry
Keep your Sentry SDK. Change one line.
Any Sentry SDK, in any language, can point its DSN at Vinktar. Error events land on the same pipeline as our own SDKs. Two things to know before you do it are right here.
what is discarded
Error events are stored. Transactions, sessions, replays and attachments are acknowledged and dropped. If you rely on Sentry for tracing or replay, keep it for those; the two can run side by side.
the identity join
Without Sentry.setUser({ id }) an error arrives anonymous and resolves to a hashed-IP cohort that never joins to a person. Send the same id your analytics uses, and the error, the funnel and the person are one record.
the_one_line
The DSN.
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 your project write key; the project id is in Settings
The endpoint speaks Sentry's envelope protocol and answers the way their SDKs expect, including 429 with Retry-After, so their back-off keeps working. Rate limits and the monthly error budget are the same as for our own SDKs. When you are ready for the analytics half, the browser SDK carries both on one key.