Skip to content
GitLab
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 6
    • Issues 6
    • 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
  • #29854
Closed
Open
Issue created Mar 22, 2019 by teor@teor

Missing diagnostic keys in relay lines, but the data is in the header

These keys are in the bandwidth file header, but there are not any similar keys in the relay lines:

  • recent_priority_list_count
  • recent_priority_relay_count
  • recent_measurement_attempt_count
  • recent_measurement_failure_count

Counting the number of times that a relay was put in the priority list is useful, so we can find out if a relay is not being prioritised.

Similarly, counting the number of times that we can't measure a relay is also useful.

Can we have these keys in each relay line:

  • relay_recent_measurement_attempt_count
  • relay_recent_measurement_failure_count
Assignee
Assign to
Time tracking