[tor-bugs] #8662 [Torperf]: Make Torperf log circuit failures

[Tor Bug Tracker & Wiki]

#8662: Make Torperf log circuit failures
-------------------------+--------------------------------------------------
 Reporter:  karsten      |          Owner:     
     Type:  enhancement  |         Status:  new
 Priority:  normal       |      Milestone:     
Component:  Torperf      |        Version:     
 Keywords:               |         Parent:     
   Points:               |   Actualpoints:     
-------------------------+--------------------------------------------------

Comment(by mikeperry):

 Hrmm.. We're likely to want to observe this data for some time, perhaps on
 the order of a year, at least. Looking at
 https://metrics.torproject.org/network.html#versions, it seems to take
 around 6 months or more for relays to migrate off of the previous stable
 version. If we assume client churn is similar, we're going to need to
 watch that data for at least that long (as we transition to ntor with
 0.2.4.x).

 Since reliability is tied closely to network security, I think we probably
 want to keep an eye on this data basically forever, just in case we hit
 some other load barrier that suddenly introduces lots of failure (like
 socket or TCP sourceport exhaustion).

 This makes me think that if we do go the separate file route, we want to
 publish it, too... (It could be shorter than full CIRC event logs.. We
 only want the failures vs successes right now).

 However, one option for per-line data is only listing the top 2-3 reason
 pairs so far, and then also list the remaining total under OTHER?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8662#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online