Skip to content

fix(detectors): adjust default jitter threshold to 0.2s instead of 200s#38

Closed
vatson wants to merge 1 commit into
VLprojects:masterfrom
vatson:jitter
Closed

fix(detectors): adjust default jitter threshold to 0.2s instead of 200s#38
vatson wants to merge 1 commit into
VLprojects:masterfrom
vatson:jitter

Conversation

@vatson
Copy link
Copy Markdown
Contributor

@vatson vatson commented Aug 29, 2025

Summary

The default jitter threshold in both InboundNetworkIssueDetector and OutboundNetworkIssueDetector was set to 200, which corresponds to 200 seconds. Since jitter values are reported in seconds, this default was unrealistically high and prevented correct detection of network issues.

Changes

  • Updated the default highJitterThreshold from 200 to 0.2 (200 ms).
  • Applied the fix consistently across inbound and outbound detectors.

Why

With the previous default of 200s, jitter-related issues would never be detected in practice. Using 0.2s (200 ms) aligns with realistic network conditions and makes the detectors functional.

@evgmel
Copy link
Copy Markdown
Collaborator

evgmel commented Feb 4, 2026

Closing the PR as another PR has fixed the issue with jitter units (#43). @vatson Thank you for highlighting the problem!

@evgmel evgmel closed this Feb 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants