Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • O Onionperf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • Metrics
  • Onionperf
  • Issues
  • #40031
Closed
Open
Issue created Sep 16, 2021 by Ana Custura@acute🚀Maintainer

Onionperf loses all state at midnight

We have some experiments that keep or discard measurements based on the CBT state (whether the CBT is computed or not at the time of measurement). This is parsed from the logs at analysis time.

However, the logs are rotated at midnight. This means that if the CBT state changed in the logs for the previous day, this is not carried over - and measurements are discarded when they should not be. I've worked around this issue by making sure the instances which use guard rotation are started just after midnight, but a more robust idea is to keep some sort of state file for any values parsed from the logs that are used to filter measurements.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking