#30217: Extend CollecTor filesystem protocol for bandwidth files -------------------------------------------------+------------------------- Reporter: irl | Owner: | metrics-team Type: enhancement | Status: new Priority: Medium | Milestone: Component: Metrics/CollecTor | Version: Severity: Normal | Resolution: Keywords: tor-bwauth,tor-dirauth,metrics- | Actual Points: roadmap-2019-q2 | Parent ID: #21378 | Points: Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by juga): Replying to [comment:1 teor]: > We thought about adding a scanner name. And now I can't remember why we didn't. Maybe juga knows? I think i didn't included just because i don't remember talking about that. I realized that some identifier would be useful in #29355. So, there are 2 options to identify the scanner: - 1. Include the nickname. The scanner does not run when some options have not been edited, but it's not the case of the nickname. I could change the configuration parser to force editing a nickname. It's human readable. Since we would only have ~10 scanners (unless we start having more than 1 scanner per dirauth), should be unique. - 2. Include the UUID (#29355). It gets created automatically the first time and it's unique but not human readable. Which one would we prefer?, both?. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30217#comment:2> 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