Opened 10 months ago

Last modified 7 hours ago

#31422 needs_review enhancement

Make BridgeDB report internal metrics

Reported by: phw Owned by: phw
Priority: Medium Milestone:
Component: Circumvention/BridgeDB Version:
Severity: Normal Keywords: s30-o21a1, anti-censorship-roadmap-2020
Cc: phw, cohosh, metrics-team Actual Points:
Parent ID: #31274 Points: 2
Reviewer: Sponsor: Sponsor30-can

Description (last modified by phw)

We're done with #9316, which means that we have code in place that allows BridgeDB to export metrics. So far, all metrics are user-centric, meaning that they focus on how BridgeDB users interact with the system. BridgeDB-centric metrics would help us debug and understand BridgeDB. The following come to mind:

  • Number of bridges per distribution ring.
  • Number of bridges per transport, similar to assignments.log (originally proposed in #14453)
  • Number of requests for which we had no bridges.

We could also incorporate bridge assignments in our metrics, so we don't have to report them separately in the assignments.log file (see #29480). Let's not forget to update BridgeDB's metrics specification.

Child Tickets

Change History (12)

comment:1 Changed 10 months ago by phw

Description: modified (diff)

comment:2 Changed 8 months ago by phw

Keywords: s30-o21a1 added
Parent ID: #31274

comment:3 Changed 6 months ago by phw

We briefly discussed this in today's anti-censorship meeting. Some additional metrics we may want to add:

  • The number of users a single bridge has been given to over time, i.e., how long to give to 10 users, how long to give to 100, how long to give to 1000, etc.
  • Once we have the ability for BridgeDB to test if bridges are down (see #31874), it would be nice to know how reliable our bridges are (how much uptime they have or how many are currently working).
  • A way to measure if the bridge is reachable from certain locations (see #32740).
  • The number of IPv4/IPv6 requests.
Last edited 4 months ago by phw (previous) (diff)

comment:4 Changed 4 months ago by phw

Description: modified (diff)

comment:5 Changed 4 months ago by gaba

Keywords: anti-censorship-roadmap-2020Q1 added

comment:6 Changed 2 months ago by phw

Cc: cohosh metrics-team added

comment:7 Changed 2 months ago by phw

Owner: set to phw
Status: newassigned

comment:8 Changed 2 months ago by gaba

Keywords: metrics-team-roadmap-2020April added

comment:9 Changed 5 weeks ago by phw

FYI, I have work-in-progress code for this in my enhancement/31422 branch.

comment:10 Changed 4 weeks ago by gaba

Keywords: metrics-team-roadmap-2020 added; metrics metrics-team-roadmap-2020April removed

Changing keyword to keep it in the metrics roadmap for when is ready.

comment:11 Changed 4 weeks ago by gaba

Keywords: anti-censorship-roadmap-2020 added; anti-censorship-roadmap-2020Q1 metrics-team-roadmap-2020 removed

comment:12 Changed 7 hours ago by phw

Status: assignedneeds_review

I think it's time for a review of what I've done so far:

Here are the internal metrics that the patch is currently capturing:

  • Number of IPv4/IPv6 requests.
  • Min, max, median, and stdev of the number of users that bridges were handed out to.
  • The number of empty responses per distributor.
  • The number of bridges per (sub)hashring.

In the meanwhile, I'll spend some more time thinking about the other metrics suggestions in this ticket.

Note: See TracTickets for help on using tickets.