Skip to main content

Core concepts

This page defines the words the rest of the manual uses. They're the same ones you see in the app.

Organization and projects​

An organization is your company or your team inside Collector. It has a name and an address of its own, /o/<organization>, and inside it are its projects and its members.

Accounts are created by invitation: someone in the organization invites you by email, and when you accept you become a member. A new organization starts with a link the Collector team sends; see Create your organization. You can belong to several organizations; you switch between them from the top bar.

A project is an application that reports to Collector: your shop, your API, your internal dashboard. Each project has its own key, its issues, its logs and its speed. When one application has a frontend and a backend, the usual setup is a project for each, or a single one if you'd rather see everything together: Collector tells what comes from the browser apart from what comes from the server.

Roles​

Every member has one of three roles in the organization:

RoleWhat it can do
Member (member)See everything: projects, issues, logs, speed, members. Resolve, ignore, reopen and assign issues.
Admin (admin)All of the above, plus invite people, change roles and remove members (never an owner), create and rename projects, rotate their DSN and manage their tokens and keys. Sees the audit log.
Owner (owner)Everything, including changing or deleting the organization and deleting projects. The only one who can make someone else an owner.

Every page of this manual that documents a screen shows, next to its title, the least role that uses it.

Events and issues​

An event is an error that happened once: an exception with its stack trace, or a message your application chose to report. The SDK sends it the moment it happens.

Identical events are grouped into an issue. Two events are identical when they have the same fingerprint: the exception's type and the functions of your own code it went through. If the error happens a thousand times, you see one issue with a thousand events, not a thousand issues. Grouping has the full rule.

Every issue has a status:

  • unresolved: it's happening and nobody closed it. Every new issue starts here.
  • resolved: someone fixed it. If it happens again, Collector reopens it and tells you.
  • ignored: known, and it doesn't matter. Its events keep counting, but it doesn't alert.

And a level, the level of the event that opened it: fatal, error, warning or info.

Environment and release​

Every event can carry an environment (environment: production, staging, …) and a release (release: the version number or the git sha). Filters and counts are per environment, and the release is what ties a minified error to that build's source maps.

Signals​

Besides errors, the SDKs say the application is alive: a signal when it starts and one every hour from servers; from the browser, one a day per release and environment. Collector shows the last signal of each environment, separately for servers and browsers, and emails you when a project's servers go quiet. Every event counts as a signal too. See Signals.

Speed​

With speed measuring on, the browser SDK measures how long pages take for your real visitors. Each page view carries its Web Vitals and the requests the page made; a visit is everything one tab did, page after page. The Speed tab gathers them by page, by request and by visit. See Speed.

Logs​

With logs on, your servers send their log lines, every HTTP request they serve and their sign-in attempts. They're for following what happens and for catching attacks: sign-in abuse, scanning, unusual volume. See Logs.

The four credentials​

Collector uses four different values for four different jobs. Mixing them up is the most common setup mistake.

CredentialLooks likeWhat forSecret?
DSNhttps://clt_…@app.clt.chrom.arSending errors, signals and page views. It carries the project's key and says where Collector is.No. It goes in browser code.
Server keyclts_…Sending logs, from your servers or from OpenTelemetry.Yes.
Upload tokencltu_…Uploading source maps from your CI.Yes.
Access tokencltp_…Using the collector CLI, the API or an AI agent, acting as you.Yes.

The first three belong to the project and are made by owners and admins; see Keys and tokens. The access token is yours: collector login makes one, or the Access tokens section of your account.