Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dashboard widgets timing out after refreshing #84167

Open
narsaynorath opened this issue Jan 28, 2025 · 2 comments
Open

Dashboard widgets timing out after refreshing #84167

narsaynorath opened this issue Jan 28, 2025 · 2 comments

Comments

@narsaynorath
Copy link
Member

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  1. Navigate to a dashboard (best reproduced using a dashboard with multiple widgets and a larger time range)
  2. Refresh multiple times, waiting for the dashboard to trigger some requests
  3. Alternatively, make a few edits e.g. changing the time range multiple times, or going back and forth between the widget builder and dashboard

Expected Result

The dashboard widgets load successfully.

Actual Result

After a few refreshes, the dashboard widgets will start to timeout and render the following banner text in the widget:

Query timeout. Please try again. If the problem persists try a smaller date range or fewer projects. Also consider a filter on the transaction field if you're filtering performance data.
Image

Product Area

Dashboards

Link

No response

DSN

No response

Version

No response

@getsantry
Copy link
Contributor

getsantry bot commented Jan 28, 2025

Routing to @getsentry/product-owners-dashboards for triage ⏲️

@narsaynorath
Copy link
Member Author

narsaynorath commented Jan 28, 2025

The reason these timeouts get hit is because we enforce limits on how much data a single organization-project combination can request data in a 10 minute window. There are a few problems that can be tackled here.

  1. Better error messaging for this issue
  2. Investigate whether the queries are necessarily taking up as much resources as they should be and if there is excessive usage, reduce that overhead so we can fit more queries in the request window
  3. Improve caching on both the frontend and backend to reduce how often we hit the DB

We need to dedicate some time to investigate and build a plan to concretely tackle these issues. For 3, the occurrence of this when editing the dashboard (e.g. navigating between the dashboard and widget builder) will be less when the redesign (see #81292) fully GAs because users will not have to navigate back and forth anymore.

This ticket serves as a log to track any progress we are making towards this issue. It currently needs to be triaged and assigned a DRI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant