Sentry
An error tracker sees stack traces, user identifiers and sometimes rather more than it should. Urengi treats the error pipeline as a sub-processor: which projects send to it, where the data lands, and who can read it.
- Category
- Cloud & security
- Auth method
- Internal integration token
- Direction
- Read-only
- Sync frequency
- Daily
- Scopes requested
- 3
- Available on
- Growth and Enterprise
- Maintained by
- Urengi
What the Sentry integration does
Three reads that treat observability as data processing, which is what it is.
Projects and their region
Each project is recorded with the region its events are stored in, which is the sub-processor answer your DPA has to make.
Scrubbing settings as evidence
Whether PII scrubbing is on, and what it covers, lands on the review — the control that decides how bad a stack trace can get.
Member access is reviewed
Who can read production errors is an access question. Urengi records the member list so it is reviewed rather than assumed.
Exactly what Urengi can see
Three read-only scopes on the organisation you select. No event bodies are read.
Urengi reads
- Project names and storage regions
- Data-scrubbing and retention settings
- Organisation member names and roles
Urengi writes
- Nothing — this connection is read-only
Urengi never touches
- Event bodies, stack traces or breadcrumbs
- User identifiers inside events
- Source maps or uploaded artifacts
- Anything after you revoke the token
Connect it in four steps
One authorisation, one field mapping, and a test sync you run yourself.
01
Authorise the connection
Open Sentry from this page and approve the scopes listed above — OAuth in a browser tab, or a scoped API key you paste. An admin approves them once.
02
Choose what syncs
Pick the projects, spaces or accounts Urengi should watch. Narrow is fine to start with; widening it later does not re-authorise anything.
03
Map your fields
Match owners, cost centres and tiers to what Urengi already tracks. Defaults arrive pre-filled from the first sync, so most teams change nothing.
04
Run a test sync
Pull one record and check it landed on the right review. The audit entry confirms the mapping before a real vendor is touched.
Your token, your rules.
Urengi stores the Sentry token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Sentry and every Urengi write stops within seconds — the audit log keeps the history, the connection simply ends.
Read the security statement- SOC 2 Type II
- audited annually
- Per-tenant keys
- no shared secrets
- Revocable in Sentry
- one click, no ticket
- EU or US residency
- chosen at signup