Re: [tor-bugs] #7652 [Metrics Website]: Can we remove relay flags graph on hourly detail?

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#7652: Can we remove relay flags graph on hourly detail?
-----------------------------+----------------------------------------------
 Reporter:  karsten          |          Owner:  karsten
     Type:  enhancement      |         Status:  new    
 Priority:  normal           |      Milestone:         
Component:  Metrics Website  |        Version:         
 Keywords:                   |         Parent:         
   Points:                   |   Actualpoints:         
-----------------------------+----------------------------------------------

Comment(by karsten):

 Replying to [comment:1 bastik]:
 > I assumed that the hourly detail on the flags existed to see/check if
 there were any glitches in the consensus.
 >
 > Authorities get together once an hour; if there's something wrong and
 half the stable relays lose their stable flag for an hour the hourly graph
 would show that, while the daily does not. At least not that clear. (Is
 there another way to see something like that happening?) For me it was THE
 reason it would exist. Sudden changes, where one would look into the
 consensus of this hour. (Were there other reasons it existed?)

 Yes, you would see sudden changes to a single relay flag, like Stable, but
 also sudden changes to the absolute number of relays.

 > (For example if the graph shows 20 more relays with the running flag
 than in the previous hour it wouldn't be a good indicator to say 20 relays
 joined in that hour, because it could be 30, as 10 left.)

 True, but if a large number of relays joins the network, it's very likely
 that you'd see it.  Or rather, it's highly unlikely that an almost equal
 number of relays would leave the network in the same hour.

 So, to answer your question how you'd detect glitches in the consensus,
 here are three services or service ideas doing that:

  - The consensus-health service tells you whether there are problems with
 the consensus process.
  - atagar's consensus-tracker service looks out for new relays adding
 unusual amounts of bandwidth to the network at once.
  - atagar and Runa were planning to extend the consensus-tracker service
 to do advanced checks for unusual things happening in the Tor network.
 There's no code for this service yet, and I don't think anybody's working
 on it right now.

 > I get the scaling part, but what prevent adding new graphs (if hourly is
 kept for the flags)?

 It would be possible to add new graphs on hourly detail, but that
 contradicts the original goal of this ticket, which is to make the metrics
 database scale better.

 Thanks for your feedback!

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7652#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs