Skip to main content

SDKs

An SDK is the package you install in your application so it reports to Collector. It captures errors on its own, notes what happened before each one, sends the signals and, if you turn them on, speed and logs.

Which one to use​

Your applicationSDKErrorsSignalsSpeedLogs
Elixir, Phoenixcollectoryesyes—yes
Node: Express, Next.js, any server@chrom-ar/collector-nodeyesyes—yes
The browser: React, Vue, Svelte, Angular, no framework@chrom-ar/collectoryesyesyes—
Any application with OpenTelemetrynone———yes
Any other languageover HTTPyesyes—yes

If your project has a server and a web page, install both: the server's and the browser's. Each sends its own to the same project, and Collector tells where each event came from.

What they all share​

  • The DSN: they all read COLLECTOR_DSN. Without a DSN they send nothing, so dev and tests stay quiet with nothing to configure. See Core concepts.
  • Environment and release: environment and release. Issues are counted per environment, and the release ties errors to source maps.
  • The user: an id, never personal data. That way every issue says how many users it affected.
  • What your code is: each SDK decides which stack frames are yours, and that decides how errors group.
  • beforeSend: sees each event last and can change it or drop it.
  • They never slow your application down: they send in the background, retry without duplicating, and slow down when Collector asks.
  • A test: each has its way of sending a test event and showing what Collector answered. collector test does the same from the terminal.