Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #18627
Closed
Open
Created Mar 25, 2016 by Arlo Breault@arloDeveloper

Run a separate websocket server reporting the transport as "snowflake"

Also, maybe we also need to spin up a pretty much identical but separate websocket server, to more easily measure the number of snowflake proxies available?

If we wanted to purely count Snowflake users, does it make sense to spin up another websocket server and maybe label it as "snowflake" instead? Is there anything special we need to do to get it displayed on the metrics website?

This is what we should do. (I meant to do it already...) It will be a websocket server but will record users as snowflake.

Assignee
Assign to
Time tracking