Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Network Health
  • sbws
  • Issues
  • #40120
Closed (moved) (moved)
Open
Created Jan 14, 2022 by juga@jugaMaintainer

Figure out why there're server descriptors without observed bandwidth

As commented at #40116 (closed), the reason for this might be that sbws is configured to gett "early", "useless" descriptors or it doesn't check the running (and others) flag or relay in dormant mode (#33166 (moved)).

Though this currently doesn't affect sbws reporting (we aren't scaling relays without this data), it'd be nice to know exactly why this happens.

Assignee
Assign to
Time tracking