[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #7359 [Tor]: Design/implement method for collecting/reporting statistics

#7359: Design/implement method for collecting/reporting statistics
------------------------------------------------------------------------+---
 Reporter:  robgjansen                                                  |          Owner:                    
     Type:  enhancement                                                 |         Status:  new               
 Priority:  normal                                                      |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor                                                         |        Version:                    
 Keywords:  performance, simulation, statistics, tor-relay, tor-client  |         Parent:  #7357             
   Points:                                                              |   Actualpoints:                    
------------------------------------------------------------------------+---

Old description:

> I envision a stats module that is responsible for processing all
> statistics gathered anywhere in Tor. This module would be responsible for
> making decisions on where they get published (ORPort, DirAuth) and how
> much scrubbing/aggregation is required for those destinations.
>
> If we like that approach, implementation likely involves porting
> currently collected stats to use the new "stats module knows best".
>
> I'll be working in my github repo in branch "morestats":
> https://github.com/robgjansen/torclone.git

New description:

 I envision a stats module that is responsible for processing all
 statistics gathered anywhere in Tor. This module would be responsible for
 making decisions on where they get published (ControlPort, DirAuth) and
 how much scrubbing/aggregation is required for those destinations.

 If we like that approach, implementation likely involves porting currently
 collected stats to use the new "stats module knows best".

 I'll be working in my github repo in branch "morestats":
 https://github.com/robgjansen/torclone.git

--

Comment(by robgjansen):

 Should we be taking the approach of sending events to the ControlPort and
 letting an external process turn them into statistics for anything that
 we're not sending up to daddy? Or are we OK with doing the stats inside of
 Tor itself. I'm personally in favor of the latter as it minimizes effort
 required to get useful stats and requires less duplication of code in the
 long run.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7359#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