Opened 2 years ago

Last modified 6 days ago

#21315 new enhancement

publish some realtime stats from the broker?

Reported by: arma Owned by:
Priority: Medium Milestone:
Component: Obfuscation/Snowflake Version:
Severity: Normal Keywords:
Cc: metrics-team Actual Points:
Parent ID: #29461 Points:
Reviewer: Sponsor:


How many snowflakes are there registered right now and happy to serve censored users?

Right now there's a big difference between 0 and 1, and it's not easy to figure out which it is.

Knowing this number would help me as a snowflake volunteer decide whether I am needed, and whether to do advocacy at this moment to get other people to be snowflakes.

Knowing this number would help the censored users too, because it would give them a sense of the health of the snowflake population, and also it can help them debug their "it's not working, I wonder if I can narrow down some possible problems" situations.

Child Tickets

Change History (4)

comment:1 Changed 2 years ago by arma

I would also be interested in stats about users and usage (including e.g. number of users being handled divided by number of snowflakes handling them), but I recognize anything involving the users is a more complicated topic, and we shouldn't do things that could put users at risk without sorting through what we ought to protect and how we can make sure it's being protected.

So, step one, tell me more about the snowflakes please. :)

One other concrete thing that I want: how many times are you giving snowflakes out? How many times did you stop giving a snowflake out because you've given it out so many times already? These questions tie into the address distribution algorithm question: it's not clear how to pick the right parameters in a vacuum, but we're not *in* a vacuum, so maybe we can gain some intuition by seeing how things play out in practice.

comment:3 Changed 11 months ago by dcf

There's an undocumented /debug URL path that shows the currently connected snowflakes. (App Engine broker that we plan to move away from) (standalone broker from #22874)

I'm not sure it's a good idea to publish this information in this form, but for what it's worth, that's how it works now.

There should be at least 3 snowflakes on each broker at all times, because we're specifically running some fallback proxy-go instances. Obviously these are no good from a circumvention point of view, because they're on a static IP address--they're mainly there so that curious people who try the snowflake option in the alpha browser aren't immediately discouraged.

comment:4 Changed 6 days ago by irl

Cc: metrics-team added
Parent ID: #29461

Metrics Team expects to produce the corresponding CollecTor module for this within the next 6-month roadmap.

Note: See TracTickets for help on using tickets.