getsentry / getsentry/sentry

Feature request: Expanding metrics retention

Open
#114,069 8 comments 3 reactions 0 assignees View on GitHub
Good First Contribution Product Area: Explore Type: Improvement
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

Metrics supports a reduced fidelity tier > 30 days, but the explore UX shows an error when trying to select a greater range. We should make it clear that it is an option, but that reduces fidelity.

### Problem Statement

Hi. I created a support case recently to allow increasing the retention period for metrics.

> Hi team. We've been using the metrics product and really like it. However, 30 days of retention is not good enough for us since we want to be able to look at trends (we're ok with metrics beyond 30 days to be aggregated on broader intervals if this makes storage easier).
>
> I don't see a way to upgrade metrics (seems like it's still in beta). Is there any way that we can get this expanded?

The suggestion was to file an feature request here. Let me know if you need more information.

### Solution Brainstorm

*No response*

### Product Area

Explore

Contributor guide

Open the contributing guide

Research direction

Start in the Explore area and trace the metrics range-selection flow, including how retention beyond 30 days is represented. Verify the behavior by selecting a range greater than 30 days: the option should be available and clearly explain the reduced fidelity instead of showing an error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.