[pbhandari]

Fixes EAP-865

MODE_LOW_PRIORITY uses the same OutcomesBased path as MODE_NORMAL, but starts at TIER_8 instead of TIER_1. Further downsample to TIER_64 / TIER_512 still happens when ingest is too large.

https://linear.app/getsentry/issue/EAP-865/add-the-ability-to-query-low-fidelity-data

[linear-code]

EAP-865

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 406c7ef. Configure here.}

[cursor]

Low priority flagged as routing mistake

Low Severity

MODE_LOW_PRIORITY now starts at TIER_8 by design, but _emit_routing_mistake still treats any non-TIER_1 query that finishes under the sampled-too-low threshold as a routing_mistake. Fast low-priority queries will emit false sampled_too_low metrics.

Additional Locations (1)

• snuba/web/rpc/storage_routing/routing_strategies/storage_routing.py#L704-L718

 

^{Reviewed by Cursor Bugbot for commit 406c7ef. Configure here.}

[onewland]

I think you still want to have some floor for small customers before we shift off TIER_1. Product relies on us to know total ingest volume; we can't rely on them only sending LOW_PRIORITY for big customers.