Opened 5 months ago

Last modified 5 weeks ago

#31422 new enhancement

Make BridgeDB report internal metrics

Reported by: phw Owned by:
Priority: Medium Milestone:
Component: Circumvention/BridgeDB Version:
Severity: Normal Keywords: metrics, s30-o21a1
Cc: phw 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).

Child Tickets

Change History (3)

comment:1 Changed 5 months ago by phw

Description: modified (diff)

comment:2 Changed 4 months ago by phw

Keywords: s30-o21a1 added
Parent ID: #31274

comment:3 Changed 5 weeks 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).
Note: See TracTickets for help on using tickets.