Resolving Signoz Dashboard Blank Screen Issue
TLDR Sumanth faced a blank screen error on Signoz after adding a new panel to dashboard. Prashant suggested retrieving the dashboard JSON to examine for errors and provided a potential workaround. Issue remains unresolved.
Jul 17, 2023 (4 months ago)
Sumanth
07:26 AMI just added a panel to a dashboard of mine on signoz, i think some error has happened because getting a full white screen. The following is a screenshot of the screen and the console log errors. How do i fix this? If someone could direct me on how to find code for the panels added to a dashboard, i could delete the panel i recently added and bring back this dashboard.
Please direct me on how to find and delete panels of a dashboard through non gui means.
Prashant
08:03 AMso that we can evaluate what is not right with it.
cc Srikanth Palash
Sumanth
08:17 AMHow do i get the dashboard json? im unable to open the dashboard, thats when the screen goes white
Prashant
08:17 AMSumanth
08:19 AMSumanth
08:22 AM"title": "429 Retry status codes hourly interval - Copy"
this is the panel i added last that caused the issue
Sumanth
08:38 AMSumanth
11:11 AMPrashant
03:18 PMcc Palash Gupta
Prashant
03:22 PM{...}
section) from the JSON.Followed by following
PUT
call:curl '' \
-X 'PUT' \
-H 'Authorization: Bearer BEARER-TOKEN-HERE' \
-H 'Content-Type: application/json' \
--data-binary @'./mydashboard.json'
Replace
BEARER-TOKEN-HERE
with bearer token from any authenticated API calls in network tab.Jul 18, 2023 (4 months ago)
Srikanth
04:15 AMSumanth
07:05 AM{"status":"error","data":"Error reading request body","errorType":"bad_data","error":"title not found in post data"}%
i tried modifying the original payload by removing the unwanted dashboards and also removing "success" field and removing "data" key and opening up the object, still facing same error message
SigNoz Community
Indexed 1023 threads (61% resolved)
Similar Threads
Extracting Custom Fields as Attributes from Log in SigNoz
Harald wants to have custom fields from their body parsed as attributes in the SigNoz logger. They have tried implementing suggestions from nitya-signoz and Prashant, but the issue remains unsolved due to a potential race condition encountered while executing the code. They have provided a full example using Kind for further assistance.
Dashboard Load Issues and Possible Solutions
Al experiences dashboard loading issues since updating to `0.18.1`. Srikanth believes the issue is not version related and suggests examining queries, memory resources, and server distribution for improvements.
Issues with Signoz 10.2: Grouping, Missing Traces, and Capturing Requests
Anil reported issues with Signoz 10.2, including grouping, missing traces, and capturing requests. Srikanth suggested upgrading to a newer version. The issue was resolved after upgrading the node version to 18 and additional clarifications were provided.
Displaying MongoDB Atlas Metrics on Signoz Dashboard
Div is unable to display MongoDB Atlas query time data on Signoz Dashboard. Ankit and vishal-signoz suggest checking compatible versions and using different packages, but the issue remains unresolved.
Issues with SigNoz Setup and Data Persistence in AKS
Vaibhavi experienced issues setting up SigNoz in AKS, and faced data persistence issues after installation. Srikanth provided guidance on ClickHouse version compatibility and resource requirements, helping Vaibhavi troubleshoot and resolve the issue.