Skip to content

feat(tracemetrics): Use configured standard retention for max pickable days - #131468

Draft
sentry-junior[bot] wants to merge 3 commits into
masterfrom
feat/tracemetrics-retention-picker
Draft

sentry-junior[bot] wants to merge 3 commits into
masterfrom
feat/tracemetrics-retention-picker

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

In SaaS, the trace metrics (Application Metrics) date range is hardcoded to 30 days, so orgs that have a longer trace metrics retention configured can't pick a range that reaches it.

The TRACE_METRICS case in the gsApp useMaxPickableDays override now uses the subscription's effectiveRetentions.traceMetric.standard, with 30 days as the floor. It ignores downsampled on purpose: every plan includes 13 months of downsampled trace metrics retention, and that may be removed, so we don't want everyone's picker to open up to it. standard is 30 on every plan unless an org-wide or per-category retention override is set, so only orgs with an explicit longer retention see a change.

No feature flag. The override itself is the gate, so #131466 and #131467 are closed. Changing the default for all orgs waits until the downsampled retention decision is made.

Open decisions:

  • Scope: the shared hook also raises the limit on the Explore metrics page, not just dashboards. Explore owners should OK that.
  • Attributes past 30 days: the attribute list will still be empty for ranges older than 30 days, because the Snuba co-occurring attributes index only keeps 30 days. That needs a separate fix in the trace item attributes endpoint.

via @DominikB2014.

--

View Session [Sentry]

… behind a flag

With organizations:dashboards-tracemetrics-90-day-range, trace metrics
date pickers allow the org's trace metrics retention, capped at 90 days,
instead of a fixed 30 days.

Co-Authored-By: Dominik Buszowiecki <44422760+DominikB2014@users.noreply.github.com>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 17, 2026
sentry-junior Bot and others added 2 commits November 20, 2026 21:25
…etention-picker

Co-Authored-By: Dominik Buszowiecki <44422760+DominikB2014@users.noreply.github.com>

# Conflicts:
#	static/gsApp/overrides/useMaxPickableDays.tsx
…e days

Drop the dashboards-tracemetrics-90-day-range flag and the downsampled
retention. Every plan includes 13 months of downsampled trace metrics
retention, which may be removed, so only a configured standard retention
longer than 30 days raises the date picker limit.

Co-Authored-By: Dominik Buszowiecki <44422760+DominikB2014@users.noreply.github.com>
@sentry-junior sentry-junior Bot changed the title feat(tracemetrics): Use trace metrics retention for max pickable days behind a flag feat(tracemetrics): Use configured standard retention for max pickable days Nov 20, 2026

This branch was successfully deployed

1 active deployment
Preview — 9503d4f6 Deployed Nov 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant