Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #29854

Closed (moved)
(moved)
Open
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
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking