#31780: Write a specification for BridgeDB's metrics ------------------------------------+------------------------------- Reporter: phw | Owner: phw Type: task | Status: merge_ready Priority: Medium | Milestone: Component: Circumvention/BridgeDB | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: 0.5 Reviewer: cohosh | Sponsor: Sponsor30-can ------------------------------------+-------------------------------
Comment (by phw): Replying to [comment:11 karsten]: > Replying to [comment:9 phw]: > > Here's an implementation quirk that I just realised: When I restart BridgeDB (e.g., to update to the latest version), it does not write its unfinished metrics to disk, which means that we are losing up to 24 hours worth of metrics after each restart. I filed #31936 for this issue. > > Relays have the same issue. The downside of writing unfinished metrics to disk is that having non-sanitized metrics on disk can be a security problem. This is why relays keep non-sanitized statistics in memory, then sanitize them, and then write them to disk. Of course it's unfortunate to lose up to 24 hours worth of metrics because of a restart, but for relays this hasn't caused major trouble in the past. Maybe this is different with BridgeDB, though. [[br]] Thanks for the context, that's helpful to know. [[br]] > Anyway, this is unrelated to making BridgeDB stats/metrics available, right? If so, I'd continue with adding these stats/metrics to metrics-lib and CollecTor. [[br]] Yes, it is. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31780#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