getsentry / getsentry/sentry

Allow time range filters with fixed start date but open end date in discover queries

Open
#95,103 3 comments 0 reactions 0 assignees View on GitHub
3. Medium Improvement
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Problem Statement

A discover query can have a time range filter applied. In the filter one could specify both start and end date, or only end date - by applying "last X days" filter. However, when you run experiments it's very convenient being able to monitor their tech metrics in Sentry. The problem is that running experiments have fixed launch date, but open end date.

This can be worked around by putting something like `timestamp:>experiment_start_date` into the query itself. But this approach clutters the query and is not consistent with other time filter scenarios.

Image

### Solution Brainstorm

Add another time range filter, which would let to specify a start date, but leave the end date open and basically equal to "now".

### Product Area

Unknown

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by locating the Discover query time-range filter and its query construction, then trace how a fixed start date and an open end date are represented. Done means users can set a start date with the end implicitly equal to now without adding a timestamp condition to the query.

Written by the indexing model from the issue text.

Assessment

Domain
analytics
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.