getsentry / getsentry/sentry

Widget-specific Time Intervals

Open
#122,732 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Problem Statement

We've been trying to use Sentry dashboards to review the health and performance of our systems, but navigating them correctly has been tricky. We've got specific reports we'd like to show to our executives that show comparative performance, can't do it with a single link.

For example, for our primary feature, we'd like to show a report that includes:

  • Trailing 30d performance
  • Trailing 7d performance
  • Trailing 24h performance

It's the same query all 3 times, but we'd like to show it as 3 distinct widgets on the same dashboard. The 3 views can all be achieved now by manually selecting the dashboard window 3 times, but that's more error prone than you might expect for folk that aren't deeply familiar with Sentry's UI.

Solution Brainstorm

We can get the exact functionality we want by either of the following:

  • Added support to hardcode a time interval for single query on a widget
  • Added support for a hardcoded time interval on the entire widget

Query specific time intervals would be awesome but I'm guessing are a lot harder. Widget specific time intervals would be sufficient for our current use case, but either would be 💯 !!!

Product Area

Dashboards

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Sentry Dashboards product area and compare the two proposed scopes: widget-level intervals and query-level intervals. Define which interval behavior is required for the three example views and consider how completion would be verified in a dashboard containing the same query at 30-day, 7-day, and 24-hour ranges.

Written by the indexing model from the issue text.

Assessment

Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.