Fix overview unselected metrics to use data-adaptive window#174
Merged
Conversation
When no time filter is set, headline metrics and charts now infer span from recent telemetry (last 10k events/errors, clamped 7–90 days) instead of a fixed ~840-day calendar window. Lists remain all-time. Co-authored-by: Cursor <cursoragent@cursor.com>
cf8ae36 to
433ec5e
Compare
This was referenced Jul 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes confusing ~840-day metrics window when Overview time range is left unselected.
Recommendation (options evaluated):
Before: Unselected range set
bucket: weekandeffectiveIngestRateDurationMs=120 × 7 days≈ 840 days for headline metrics, compare deltas, and ingest-rate denominators — regardless of whether the project had 100k events/day or 1/day.After: With no time filter:
metricsSince,metricsUntil,metricsDurationMs; dashboard uses the server-computed duration for ingest-rate displayChanges
overview-metrics-window.tswithresolveUnselectedMetricsWindow()and unit testsresolveCompareWindow(metricsWindow.durationMs, …)but with the resolved adaptive duration/docs/dashboard)Test plan
pnpm lint && pnpm test && pnpm buildMade with Cursor