Sentry
Read your Sentry project issues into your app to show what is breaking.
Connecting
Create a token in Sentry under User settings > Personal Tokens, with the event:read scope.
Read project issues
- org: Your Sentry organization slug, as it appears in your Sentry URL. Required.
- project: The Sentry project slug to read issues from. Required.
- query: A Sentry search, like is:unresolved. Unset reads unresolved issues.
- sort: The order issues come back in. date is newest first.
- limit: How many issues to read, up to 100. The first one lands in the table.
Answers with: id, short_id, title, culprit, level, status, count, user_count, first_seen, last_seen, permalink.
Settings
- Organization: Your Sentry organization slug, used when a call names none.
- Project: The Sentry project your app reads by default, by its slug.
- Search: The Sentry search applied when a call names none, like is:unresolved.
What it stores
Issues (id, short-id, title, culprit, level, status, count, user-count, first-seen, last-seen, permalink, org, project)
Where it speaks
This connection reaches https://sentry.io and nowhere else. The hosts are fixed by declaration.