Hm, feature request: give me a way to learn more about the errors: “JsonRpcConnector error: val…” and “Received http2 header with s…”. I tried hovering over each one, clicking on each one (the red text), and then tried clicking on the name of the row—“Zaino (zec.rocks test)”—and nothing gave me more information about the error.
On the live dashboard, any red/yellow Issue cell or endpoint name now when clicking on details: opens the full probe error: verbatim gRPC/transport message, gRPC code, summary, likely cause, copyable raw text, grpcurl to reproduce, plus separate guidance for wallet sync debugging vs endpoint operators.
Nice! Next question: why do all of these say uptime 0% even though some of them say that they responded and have a height? And why do all of them have “Lag” or “-”?
That’s likely because they are classifying uptime strictly when the node reports status as green. Since the status is perpetually yellow as reference chain tip is unavailable, there is no uptime.
Strahncryptography’s correct without a reference chain tip poller couldn’t compute lag (“—”), and healthy uptime only counts green checks, so everything stuck yellow showed 0% even when endpoints responded with height. Fixed the reference sources and how uptime is displayed;
Historical graphs per endpoint: height, lag vs the reference tip, and latency per poll. They deepen the longer polling runs, so trends fill out over time.
Thank you for your submission. After consideration from ZCGand sufficient time for the community to provide feedback on the forum, the committee has decided to reject this proposal.
The committee appreciates your grant submission efforts and encourages you to continue as an active member of the Zcash community going forward!