Verify ingestion

Once your app has a DSN, confirm the path end to end before wiring up alerts.

From your appCopy Anchor Link

import * as Sentry from "@sentry/browser";

Sentry.init({ dsn: "https://<publicKey>@api.errordx.com/<projectId>" });

// `captureException` flushes on its own; the default SDK transport is fine.
Sentry.captureException(new Error("ErrorDX is running"));

Reload the Issues view — the event should be there within a few seconds, grouped under a new issue with its stack trace.

From a terminalCopy Anchor Link

The CLI sends the same payload the SDK does, which makes it a good way to check a DSN without touching app code:

errordx ingest --project <slug> --message "hello from the CLI"

If nothing arrivesCopy Anchor Link

• Check the DSN. The public key and the project id are both in /{orgSlug}/projects/{projectSlug}/setup; a key from another project sends the event somewhere else.
• Check the network. The SDK needs outbound HTTPS to api.errordx.com. A blocked or proxied egress path is the usual cause on corporate networks and in some sandboxes.
• Check 429s. Ingest past the monthly event budget is rejected with Monthly event quota exceeded; the current usage is in Settings → Billing. See Billing & tiers.
• Check the SDK is initialised before the error. Sentry.init has to run before the code that throws (or the error must be captured manually).

NextCopy Anchor Link

• Alerts and notifications to get told about it automatically.
• Agents & CLI to query issues from an agent.