#34218: Split PROXY errors into whatever reasons are given in TorCtl logs -----------------------------------+-------------------------- Reporter: karsten | Owner: metrics-team Type: enhancement | Status: new Priority: Medium | Milestone: Component: Metrics/Onionperf | Version: Severity: Normal | Keywords: Actual Points: | Parent ID: Points: | Reviewer: Sponsor: Sponsor59 | -----------------------------------+-------------------------- If we combine TGen transfers with Tor streams and circuits we can learn a lot more about why our proxy (Tor) failed. Including that information in visualizations might be very useful.
When we match TGen transfers with TorCtl events, we'll have to look [https://gitweb.torproject.org/metrics- lib.git/tree/src/main/java/org/torproject/descriptor/onionperf/OnionPerfAnalysisConverter.java how metrics-lib does this]. Maybe we can use some ideas from #30612 where we discussed putting an error code graph on Tor Metrics. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/34218> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs