Sentry Cost Tuning

Overview

Reduce Sentry spend by 60-95% through SDK-level sampling, server-side inbound filters, beforeSend event dropping, and quota management — without losing visibility into production errors that matter.

Prerequisites

• Active Sentry account with org:read and project:read scopes on an auth token
• Access to the project's Sentry.init() configuration (typically sentry.client.config.ts or instrument.ts)
• Current plan tier identified: Developer (free, 5K errors/mo), Team ($26/mo, 50K errors + 100K transactions), or Business ($80/mo, 100K errors + 500K transactions)
• SENTRY_AUTH_TOKEN and SENTRY_ORG environment variables set for API calls
• @sentry/node >= 8.0 or @sentry/browser >= 8.0 installed

Instructions

Step 1 — Audit Current Usage via the Stats API

Query the Sentry Usage Stats API to understand where volume comes from before making changes. This endpoint returns event counts grouped by category over any time period.