Integrations / Sentry
Sentry
Sentry application monitoring and error tracking platform
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
Permissions Telara requests
- event:readOAuth 2.0
- event:writeOAuth 2.0
- project:readOAuth 2.0
- project:releasesOAuth 2.0
- org:readOAuth 2.0
- member:readOAuth 2.0
- team:readOAuth 2.0
In Telara
Connect in Telara
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- Auth Token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Organization | Partial — not every record the vendor holds is synced |
| Incidents | Partial — not every record the vendor holds is synced |
| Releases | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Organization | Up to 1 day | Removed records disappear on the next full sync |
| Incidents | Up to 1 hour | Removed records disappear when Telara next reconciles that resource |
| Releases | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Organization, Incidents, Releases.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty