TL;DR
- A mobile app with 1M MAU and a 0.5% crash rate generates roughly 150,000 error events/month. At 5M MAU, that's 750,000 events. Sentry's Team plan includes 50,000 events, so you're paying overages or sampling aggressively.
- Sampling is primary cost control at scale, but naive sampling (capture 10% of all events) loses rare crashes that only affect specific device/OS combinations. Smart sampling captures 100% of new error types and samples down only after deduplication.
- OEM fragmentation on Android is a scale multiplier. The same crash produces 3-5 separate groups across Samsung, Xiaomi, OnePlus, and Pixel because each OEM modifies framework stack. Without custom fingerprinting rules, your dashboard shows 500 crash groups when there are 100 root causes.
- The tiered strategy that works at scale: capture 100% of fatal crashes, sample non fatal errors at 10-25%, filter out known noisy errors entirely, and gate Jira ticket creation on "affects more than N users."
Where Drizz fits:
- Drizz catches crash inducing regressions on real devices in CI before build ships. Fewer production crashes means lower event volume on your monitoring tool.
- At scale, a 30% reduction in crash causing regressions reaching production can save thousands/month on Sentry overages.
For a full feature comparison, see best mobile error tracking tools . For pricing focused evaluation, see cheapest mobile error tracking tools.
Why does error tracking break at high traffic?
Error tracking tools are designed for assumption that errors are rare. When your app hits 1M+ MAU, that assumption breaks.
A thread on r/devops about monitoring costs at scale shows pattern: teams that never questioned their error tracking bill at 100K MAU suddenly find it's a top 5 infrastructure expense at 2M MAU. The per event pricing model that felt cheap at low volume becomes unpredictable once bad releases and bot traffic enter picture.
Event volume explosion
A mobile app with 1M MAU, 3 sessions/user/month, and a 0.5% error rate generates roughly 150,000 error events/month, while Sentry's Team plan includes 50,000. At 5M MAU, you're generating 750,000+ events/month.
Every bad release spikes this further. A single regression that crashes 2% of sessions for 6 hours before you catch it can generate 50,000+ events in that window alone, consuming your monthly allocation in a fraction of time.
OEM fragmentation as a scale multiplier
On Android, Samsung, Xiaomi, OnePlus, and Pixel each inject custom framework classes into view hierarchy. The same NullPointerException produces different stack traces on each OEM, and your crash tool creates separate groups for each variant.
At 100K MAU this is manageable (you merge a few groups manually). At 5M MAU with hundreds of crash types across 15+ OEM variants each, your dashboard shows 2,000 crash groups when there are 400 root causes.
Noise drowning real problems
At scale, ratio of actionable crashes to noise shifts. Third party SDK errors, bot traffic on shared APIs, rooted device edge cases, and known won't fix issues accumulate. Without active noise filtering, engineering teams stop looking at crash dashboard within a week because every triage meeting starts with 30 minutes of "ignore this, ignore that."
How do you sample without losing rare crashes?
Naive sampling (set sampleRate: 0.1 and capture 10% of everything) is fastest way to miss a crash that only affects Galaxy A14 running Android 13 with 4GB RAM. At 10% sampling, a crash affecting 200 users out of 5M might produce 20 sampled events, which might not be enough to surface it as a distinct issue.
Tiered sampling strategy
The approach that works at scale captures different event types at different rates:
- Fatal crashes (unhandled exceptions, SIGSEGV, SIGABRT): capture at 100%. These are crashes that kill app. Never sample them down
- ANRs: capture at 100%. Google Play's ANR threshold (0.47%) means every ANR data point matters for keeping your app visible in Play Store
- Non fatal errors (handled exceptions, network errors, validation failures): sample at 10-25%. These are high volume, lower urgency events. Sampling at 10% gives you statistical significance without consuming quota
- Performance traces: sample at 1-5%. Transaction/span data is highest volume, lowest urgency data type. Most teams don't need 100% of performance traces to identify slow endpoints
Developers on r/devops discussing cheap error tracking confirm that tiered approach (100% fatal, sampled non fatal) is what makes event based pricing workable at scale. The alternative is self hosting (GlitchTip, SigNoz) to remove per event costs entirely, trading vendor support for infrastructure maintenance.
Sentry's dynamic sampling
Sentry supports trace based sampling rules that let you define different sample rates by transaction type, release version, or environment. Configure in Settings → Performance → Sampling Rules.
The rule you want for high traffic mobile: sample 100% of traces for latest release (to catch regressions), 5% for stable older releases, and 0% for internal/debug builds.
SDK level deduplication
Use Sentry's beforeSend callback to filter out known noisy errors before they leave device. This is cheaper than server side filtering because event never counts against your quota.
Common filters for high traffic mobile: CancellationError (Swift Task cancellation), UnknownHostException (airplane mode), SecurityException on rooted devices, and third party SDK errors from ad networks.
Which tools handle high traffic mobile apps?
Sentry at scale
Sentry is most common choice for high traffic mobile apps when teams need crash grouping, Jira automation, and ownership routing. Managing cost at scale requires active configuration.
- Spike protection: automatically rejects events above a configurable threshold to prevent a bad release from consuming monthly allocation. Enable in Settings → Subscription → Spike Protection
- Per project rate limits: cap events per project so a noisy backend project doesn't eat quota intended for mobile app
- Dynamic sampling: different sample rates by transaction, release, or environment
- Custom fingerprinting: merge OEM variant crash groups by defining rules that ignore vendor specific stack frames (com.samsung.*, miui.*)
- Pricing at scale: Team plan ($26/seat/month) includes 50K events. Additional events at ~$0.00025/event. At 500K events/month, expect roughly $130 base + $112 in overages = $242/month for 5 seats
Crashlytics at scale
Crashlytics is free with no event limits, which makes it default for teams where cost is primary scale concern. The limitation is triage automation, not volume handling.
- No sampling needed: unlimited events mean you never lose rare crashes to sampling
- Velocity alerts: fire when a crash type affects X% of sessions in 30 minutes, which works at scale as long as your staged rollout percentages give enough session volume per version
- OEM handling: cluster key grouping sometimes splits variants, requiring manual merge. Use setCustomKey with Build.BRAND and Build.MODEL to filter OEM specific crashes in dashboard
- The gap at scale: one way Jira sync, no ownership routing, no anomaly detection. At 5M MAU, manual triage of Crashlytics alerts becomes a full time job without Sentry's automation
Native Android developers on r/androiddev choosing between Crashlytics and Sentry at scale consistently land on Crashlytics for cost and Sentry for triage. The compromise some teams make: Crashlytics for crash detection (free, unlimited) with a separate Sentry project just for critical flows (checkout, auth) where automated triage justifies per event cost.
Embrace at scale
Embrace captures 100% of user sessions without sampling, which is its primary advantage at high traffic. You don't lose rare crashes to sampling because every session is captured.
- Unsampled capture: every session, every crash, every ANR, every network call. No data gaps from sampling
- Session based pricing: based on sessions/month rather than events/month, which scales more predictably for mobile (one session can generate 10+ events if there are multiple errors)
- ANR flame graphs: at scale, ANR debugging is harder because same main thread blocking pattern produces different surface level symptoms. Embrace's continuous 100ms stack sampling identifies root blocking call even when ANR manifests differently across devices
- Free tier: 1M sessions/month, paid plans are contact us
Engineers on r/devops sharing their production monitoring stacks note that session based pricing (Embrace's model) scales more predictably than event based pricing (Sentry's model) for mobile apps, because one user session can generate 10+ error events during a bad release but still counts as one session.
GlitchTip at scale (self hosted)
GlitchTip removes per event pricing entirely. For high traffic apps where event volume makes cloud Sentry pricing impractical, self hosting is cost escape hatch.
- Sentry SDK compatible: swap DSN URL, keep your existing Sentry SDK integration. No code changes
- Infrastructure cost: runs on 4 containers (Web, Worker, Postgres, Redis) with 2 vCPUs and 2GB RAM for small medium volume. At 500K+ events/month, allocate more storage and consider a dedicated Postgres instance
- What you lose: session replay, anomaly detection, ownership routing, vendor support. The crash reporting and grouping work; advanced triage features don't exist
- Best for: teams with DevOps capacity to maintain infrastructure and no need for Sentry's advanced features
How do you build a tiered error management strategy?
At scale, not every error deserves same treatment. The tiered strategy:
Tier 1: critical (auto create Jira ticket, page on call)
Fatal crashes affecting more than 0.1% of sessions in current release version, ANRs exceeding Google Play's 0.47% threshold, and crashes in revenue critical flows (checkout, payment, authentication).
Gate: Sentry alert rule with condition "issue affects more than N users in M hours" → PagerDuty page + Jira P0 ticket auto created.
Tier 2: actionable (auto create Jira ticket, assign to release owner)
New crash types in current release, regressed crashes (previously fixed, now recurring), and non fatal errors affecting more than 1,000 users.
Gate: Sentry alert rule → Slack notification + Jira P1 ticket assigned to release owner.
Tier 3: monitor (daily digest, triage in standup)
Non fatal errors affecting fewer than 1,000 users, known third party SDK issues, and edge case crashes on rooted/jailbroken devices.
Gate: daily email digest or Slack summary. No automatic ticket creation.
Tier 4: suppress (filter out entirely)
CancellationError, UnknownHostException in airplane mode, ad SDK errors, known won't fix issues. Filter via beforeSend at SDK level so they never count against quota.
A developer on r/reactnative processing 25 million events on a Sentry alternative confirms that SDK level filtering is single most impactful cost reduction: filtering known noise before it leaves device eliminates 20-40% of event volume at scale without losing any actionable crash data.
Pricing at scale
FAQ
What is best error tracking tool for high traffic mobile apps?
Sentry with spike protection and dynamic sampling for teams that need automated triage, Crashlytics for teams that prioritize zero cost over automation, and Embrace for teams that need unsampled session capture without event based pricing.
How do you manage error tracking costs at scale?
Tiered sampling (100% fatal crashes, 10-25% non fatals, 1-5% performance traces), SDK level deduplication via beforeSend to filter known noise before it counts against quota, and spike protection to cap overages during bad releases.
How many error events does a 1M MAU mobile app generate?
At a 0.5% crash rate with 3 sessions/user/month, roughly 150,000 error events/month, and bad releases, ANRs, and non fatal errors push this higher. Sentry's Team plan includes 50,000 events, so overages start quickly at this scale.
Does OEM fragmentation affect error tracking at scale?
Yes, substantially: same crash produces 3-5 separate groups across Samsung, Xiaomi, OnePlus, and Pixel due to OEM framework modifications. Custom fingerprinting rules (ignoring vendor specific stack frames) are necessary to keep crash group counts manageable.
Is Crashlytics enough for high traffic mobile apps?
For crash detection, yes: free, unlimited events, automatic symbolication. For triage automation at scale (auto assign tickets, ownership routing, anomaly detection), no, because at 5M+ MAU manual triage of Crashlytics alerts becomes a bottleneck.
How does sampling work without losing rare crashes?
Capture 100% of fatal crashes and ANRs (never sample these), then sample non fatal errors at 10-25% and performance traces at 1-5%. Use Sentry's trace based sampling rules to sample 100% of latest release and lower rates for stable older versions.
What's cheapest error tracking option for a high traffic mobile app?
Crashlytics ($0, unlimited events) for crash detection, or self hosted GlitchTip ($10-30/month infrastructure) for Sentry compatible features without per event pricing. Both require more manual triage than paid Sentry.
How does pre release testing reduce error tracking costs at scale?
Crashes caught by E2E tests on real devices in CI never reach production monitoring. A 30% reduction in crash causing regressions at 500K events/month saves roughly $30-40/month in Sentry overages and prevents tier 1 alerts that page engineers at 2am.
