Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.backend.python beat.backend.python
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beat
  • beat.backend.pythonbeat.backend.python
  • Issues
  • #4

Closed
Open
Created Jul 11, 2015 by Laurent EL SHAFEY@laurent.el-shafey

Statistics split

The statistics are now generated by two different processes: the I/O daemon and the user process. However, everything is handled in one class, which means that statistics objects are often created but only half populated. We may consider to split the class definition of statitics object to better reflect the underlying implementation.

Assignee
Assign to
Time tracking