[Feature Request] I2PD like "Tunnel creation success rate" stat added to the Web UI

[K7pyk3M5AE2X3]

One thing that came up on the threads around this recent DDOS is people are talking a lot about the "tunnel creation success rate" and it quickly became apparent this seems to be a useful metric (in some cases) that I2PD prominently display but it's rather difficult to find in I2P without a whole lot of digging as (from: https://geti2p.net/en/docs/how/network-database) isn't very intuitive. Even if you intuit getting to the "netdb" section from that aforementioned link, it's not intuitive to then click the top/highest version.

http://127.0.0.1:7657/netdb?v=0.9.67

stat_tunnel.buildExploratoryExpire.60m = 0;0;0;53.14
stat_tunnel.buildExploratoryReject.60m = 0;0;0;15.51
stat_tunnel.buildExploratorySuccess.60m = 0;0;0;31.35
stat_tunnel.participatingTunnels.60m = 289.20

(not real values, just copied from the doc link above)

You kind of mention it "coming" in 2.10 (though it didn't) in this thread "https://i2pforum.net/viewtopic.php?t=1384" but it never made it it seems and I'm not confident it's going to be in 2.11 coming out in a couple days either. I get that it's useful as is for a well defined data structure / log to stats.i2p perspective but it's not useful to the average user trying to do basic monitoring or troubleshooting.

Suggest moving it to the sidebar somewhere, maybe as a new row under "Shared" in the "Tunnels" section.

[zzzi2p]

Don't think that forum thread has anything to do with "TCSR" as i2pd calls it.

We did add stats a couple years ago, you can select them for graphing on /configstats :

tunnel.buildClientSuccessRate
tunnel.buildExploratorySuccessRate

We have two different stats because the build strategies are very different. So neither is directly comparable to the i2pd TCSR display.

We don't put it in the sidebar, because build success is mainly an indicator of network health, not the health of your router. There's not much the user can do to make it higher, it just results in a ton of user posts like you saw recently "my TCSR is 2% what do I do???" which isn't helpful.

[K7pyk3M5AE2X3]

Fair on your last part statement but on the flipside, often, as with this recent past case, the "weather report" is slow (I don't think it's automated) and you are left wondering if in fact it's your router or the network. I get the want to minimized pointless posts like you said but equally would be nice if there was a easy way to quickly ascertain for the casual user "is it my router or the network".

Not saying this has to be the metric but something is needed because I'm not the only one that spent hours troubleshooting my local router only to find out it was the network and then getting equally annoyed because it said "network: ok" (and wasn't) all the while finding out I2PD seemed to have a useful metric that was end-user friendly to show this.

Feel free to close with "won't fix, working as expected" but I'd suggest if not this, then something that alerts the CASUAL user "hey don't waste time troubleshooting your local router, it's the network" and it ain't "network: ok" as we just seen.

Also those stats are less than helpful, I think most users read "sucessRate" as a percentage, not an absolute number nor a "response time for success in MS" (whatever that means), i.e. Avg. 5.6K means nothing to most people.