-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Widgets in the Dashboards are throwing 504 #5962
Comments
Can you check your docker compose logs of your web/nginx container? It might be helpful to see if there are any errors there. |
Have checked the logs, not seeing anything related to this. Enabled the logging to debug also, still we didnt find any log on this. Any other container logs we need to check ? Need to know how exactly the dashboards are loaded, which is the service calling the DB, we can check at that container level. Also we are confused now in which DB the dashboards data are saved and from which DB the data is pulled. Does any DB configs affect the functionality of Dashboards. |
Seeing this error exactly after 15sec, is there any hard coded connection timeout setting there. We were not able to find any configs. And meantime have seen some logs with web and snuba-api side
|
How's the memory and CPU usage on your instance when this occurs? Its possible that the snuba server is rejecting these connections due to memory issues. |
There are no resource issues seen, memory and cpu usages are fine. However have allotted more resources to this services and tried but still seeing failures. Seems something to do with timeout values and unable to find the exact config for it. |
I'm not familiar with all of the snuba settings myself. I'll forward to that team to see if anyone there has more insight. |
Could you provide a link to the dashboard? It seems like your queries are missing a project/organization id, which could be causing the connection error |
@xurui-c should allocation policy violations be occurring in self-hosted? This looks like a bug to me. |
@xurui-c its a selfhosted sentry. Also seeing this issue regularly now. Seems some config changes need to be done with snuba. Let us know if any such configuration been referred |
Hi. The snuba config which disables the allocation policy on self hosted can be found here. You can see that the allocation policy is marked as
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Self-Hosted Version
23.11.2
CPU Architecture
x86_64
Docker Version
nil
Docker Compose Version
nil
Steps to Reproduce
We have created few telemetry dashboards with different types of widgets. While checking the data with longer timestamp (20 or 30 days) most of the widgets throw 504. Exact error is like this
GET /organizations/{orgSlug}/events/ 504
Attaching the screen-shot too.
What could be the reason for this, i can find proper doc on the widget get call from which database. We tried to changes the timeout configs of clickhous, but it didnt works. Have increased the resources for postgres and clickhouse too, still issues were seen. Let us know how we can track this.
Expected Result
All widget in dashboards should load without any issue for atleast 30days of time frame.
Actual Result
nil
Event ID
nil
The text was updated successfully, but these errors were encountered: