getsentry / getsentry/sentry

Explore - Support week-over-week performance comparison with weekly time periods and intervals

Open
#107,055 4 comments 8 reactions 0 assignees View on GitHub
Improvement Product Area: Explore
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Problem Statement

Currently, performance metrics are limited to 1-day time periods and intervals, which
creates too much noise for meaningful trend analysis and reporting. Daily data is
affected by holidays, releases, reverts, and other one-off events, making it difficult
to identify genuine performance improvements over longer timeframes. This prevents teams
from accurately measuring and reporting on performance changes for OKRs and quarterly
reviews, where consistent week-over-week or quarter-over-quarter comparisons are needed
to demonstrate real progress (e.g., "we reduced LCP by X% compared to last quarter").

### Solution Brainstorm

_No response_

### Product Area

Explore

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by tracing the Explore performance-metrics implementation and defining how weekly time periods and intervals should be represented for comparisons. Done should include meaningful week-over-week comparisons, including metrics such as LCP, with behavior suitable for trend analysis and reporting.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.