#19332: Add a BridgeDB module -------------------------------------------------+------------------------- Reporter: mrphs | Owner: | metrics-team Type: enhancement | Status: new Priority: Medium | Milestone: Component: Metrics/CollecTor | Version: Severity: Normal | Resolution: Keywords: metrics-roadmap-2019-q2, ex- | Actual Points: sponsor-19 | Parent ID: | Points: 8 Reviewer: | Sponsor: | Sponsor30-must -------------------------------------------------+-------------------------
Comment (by phw): Replying to [comment:12 karsten]: > Replying to [comment:11 phw]: > > Replying to [comment:10 karsten]: > > > #9316 has been resolved recently which unblocks this ticket, AIUI. > > [[br]] > > Yes. How would you like me to expose the metrics file on BridgeDB's host? Should it be available over HTTPS? Or do you want me to rsync it to another host? > > Is there anything sensitive in the file that would have to be sanitized on the CollecTor host? If so, we should rsync it over ssh to colchicifolium. But if not, the preferred way would be to expose it on the BridgeDB host, so that others can fetch it, too. [[br]] There's nothing sensitive. We're doing the sanitisation ourselves and have [https://lists.torproject.org/pipermail/tor-dev/2019-July/013953.html published the data before]. I'll look into exposing the files over our apache. [[br]] > Here's another question, similar to the one about Snowflake stats: Would it be possible to expose more than just the latest BridgeDB statistics? Something like 7 or 14 days, or if it's not much data, everything until it gets too big? [[br]] Yes, that's definitely feasible. One week worth of data shouldn't be more than ~100 KB. I'll look into logrotate, so we can expose multiple weeks worth of data at any given time. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19332#comment:13> 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