Skip to main content

Introduction to Collector

Collector gathers what happens in your applications in one place: their errors, the signs that they're still alive, how fast their pages load, and their logs. It groups errors into issues, emails you when a new one appears or one you'd resolved comes back, and shows you what broke and why.

You use Collector from the browser, at app.clt.chrom.ar, and from the terminal, with the collector CLI.

What Collector collects​

  • Errors. Every exception your application doesn't catch arrives as an event, with its stack trace, the lines of code involved and what happened just before. Identical events are grouped into the same issue.
  • Signals. The SDKs report when the application starts and every hour after, so Collector knows it's still up even when nothing fails, and which version runs in each environment.
  • Speed. From the browser come the visits to each page, with their Web Vitals and the requests each one made.
  • Logs. Your servers' log lines, sent by the SDK or by any OpenTelemetry exporter.

Who this is for​

  • Development teams who install an SDK, receive the alerts and decide what to do with each issue.
  • Organization admins, who create projects, invite people and manage keys.
  • Platform teams who upload source maps from CI, follow logs from the terminal or use the API.

How to use this documentation​

  1. Start with the core concepts, for the terms the rest of the manual uses.
  2. Create your first project and send the first event.
  3. Pick the SDK for your language.
  4. See the technical reference for the ingestion protocol and the API.