Skip to main content

Error tracking

Tiden includes product-scoped error tracking. Runtime SDKs send exceptions to a product DSN. Tiden groups events into issues and shows them alongside releases, environments, and quality signals.

DSN keys​

A DSN is created on the product Issues setup page. It contains:

  • Public key.
  • Ingest host.
  • Product id.

DSN keys are public client credentials scoped only to ingest for that product. They are not user API tokens and cannot call the REST API.

Issues​

The Issues page shows grouped runtime problems with:

  • Title and culprit.
  • Platform and severity.
  • Times seen.
  • First and last seen.
  • Status: unresolved, resolved, ignored, or all.
  • Environment and release filters.

If events were accepted but grouping is still running, Tiden shows a processing banner and polls until issues appear.

Issue detail​

Issue detail includes:

  • Latest event stack trace.
  • Source context when source maps are available.
  • Breadcrumbs.
  • Request data.
  • User data.
  • Tags and contexts.
  • Event list.
  • Resolve, unresolve, and ignore actions.

Sensitive request headers are scrubbed before storage or presentation.

Releases and environments​

SDKs should send release and environment. Tiden uses those fields to create or resolve release and environment context for events.

Source maps​

Browser JavaScript builds should upload source maps with @tiden/telemetry-sourcemaps. The plugin injects debug IDs, uploads maps using a CI API token, and lets Tiden symbolicate minified stack traces at view time.

Source maps are private. Tiden does not expose source map download URLs to end users.