Migration guide

Altix ErrorTrack speaks the Sentry wire protocol. The official SDKs work unmodified — the only change is the DSN.

1. Create a project

Add a project in the dashboard. It gives you a DSN pointing at localhost:3102. Every event goes through that host, which is how your plan ceiling is enforced rather than reconciled later.

2. Change the DSN

Replace the Sentry DSN wherever you initialise the SDK. Nothing else changes.

JavaScript / TypeScript

import * as Sentry from '@sentry/browser'

Sentry.init({
  dsn: 'https://YOUR-KEY@HOST/PROJECT-ID',
  tracesSampleRate: 0.1,
})

Python

import sentry_sdk

sentry_sdk.init(
    dsn="https://YOUR-KEY@HOST/PROJECT-ID",
    traces_sample_rate=0.1,
)

sentry.Init(sentry.ClientOptions{
    Dsn: "https://YOUR-KEY@HOST/PROJECT-ID",
})

3. Send a test event

The dashboard has a button that sends one, so you can confirm the path end to end before you deploy. Or throw something on purpose:

Sentry.captureException(new Error('Altix test event'))

What happens at the ceiling

Your SDK keeps working. We answer 200 and drop the event rather than returning an error, because a 4xx would fill your own console with our billing problem and a 429 would make the SDK back off globally. The dashboard shows exactly how many events were turned away.

A wrong key is the one exception: that returns 401, because it is a misconfiguration you need to see immediately.

Retention

Events are removed once they pass your plan’s retention window — 7 days on the trial, 30 on Hobby and Team, 90 on Business. Issues remain; the individual events behind them age out.