Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • N Nebulo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 36
    • Issues 36
    • 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
  • PublicAndroidApps
  • Nebulo
  • Issues
  • #275

Closed
Open
Created Sep 14, 2020 by Daniel Wolf@dwolfMaintainer

Connection watchdog for packet loss is flawed

Right now the connection watchdog deems a packet loss of 30% bad.

The thing is, once the packet loss crosses this border it won't get much lower. It is calculated from the amount of failed answers and the amount of packets received from the device. With higher numbers of both the percentage isn't going to deviate much for a long time.

It should be changed to a floating average over the interval of the watchdog.

Assignee
Assign to
Time tracking