Retrieve and interpret Sentry error budget and release performance data via the Sentry API

Steps

1. Authenticate against the Sentry API using a User Auth Token or Internal Integration token with the project:read scope; all API endpoints use the base URL https://sentry.io/api/0/ for Sentry Cloud.
2. Retrieve project statistics via GET /organizations/{org_slug}/stats_v2/ with the fields parameter set to ['sum(times_seen)'] and query filtered by error, transaction, or session event types; specify the stat (events), groupBy (project), interval (1h), and date range to get time-series error counts.
3. Fetch release health data via GET /organizations/{org_slug}/releases/{version}/stats/ to retrieve crash-free session and crash-free user rates for a specific release; compare across releases to detect regressions introduced by a deployment.
4. Compute an error rate SLI from the stats API by dividing error events by total transaction events over the same time window; this approximates an availability SLI based on error occurrence without requiring Sentry-native SLO features.
5. Query transaction performance for a release via GET /organizations/{org_slug}/events/ with the query parameter scoped to transaction events, a dataset parameter of discover, and fields including p75(transaction.duration) and failure_rate() to extract latency and error rate per transaction.
6. Generate a report by iterating over releases chronologically, fetching crash-free rates and p75 latency for each, and comparing against configured thresholds; output structured data for a dashboard or post it to a reporting channel using webhooks.