-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Monitor: DAO State Head available is faulty #4166
Comments
I do agree that it doesn't make sense to have a monitoring system if we think there are so many false positives in there. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
Still relevant. |
just had a look into the issue. Seems to me like the issue is caused by a familiar face: huge amounts of data take their time on the wire. Here is a graph of a test run of the affected metric: There are some things to notice:
Here are the things to consider:
What happens if I add all seednodes:
How can we fix that?
Disclaimer:
|
http://104.248.88.175/ does request all 12 nodes with PreliminaryDataRequest and it works. Yes its also slow (see rrt) but very few errors. I guess its mainly a hosting issue. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
Description
The DAO State Head available metric shows a lot of red. We should investigate if these are legit error states or false positives.
Screenshots
The text was updated successfully, but these errors were encountered: