Core concepts

Organization (tenant)

Every account works inside a Clerk organization, which is the tenant boundary. Projects, issues, and events all belong to an organization, and the dashboard always shows the data for your active org. Switching orgs re-scopes everything; tenants never see each other's data.

Project

A logical app or service. A project owns one ingest key and scopes the issues and events sent with it.

Ingest key

A publishable key (mtr_…) that authorizes writing events into one project — nothing else. It can ship inside client code, like a DSN. Rotate it any time from project settings; the previous key stops working immediately.

Issue & Event

An event is a single reported occurrence. Events that share a fingerprint roll up into one issue, whose counters (events, users affected, first/last seen) update on every ingest.

Grouping & fingerprinting

Each event is reduced to a stable fingerprint:

• With a stack trace: by exception type plus the signature of the most relevant in-app frames.
• Otherwise: by exception type and value, or by a normalized message where volatile bits (numbers, UUIDs, hex, quoted strings) are collapsed — so User 123 not found and User 456 not found land in the same issue.

If a new event arrives for a RESOLVED issue, Metricly reopens it and flags the response as a regression.