Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

do not set sys.time.estimatedError when time is unsynchronized #131

Merged
merged 1 commit into from
May 29, 2024

Conversation

copperlight
Copy link
Collaborator

We are trying to gather some data on the accuracy of clock time across the fleet, and the sys.time.estimatedError was reporting a number of 16s values.

These values occur when the kernel has not synchonized the clock yet. This fact is tracked with the sys.time.unsynchronized metric. The estimatedError metric should only have valid results from ntp_adjtime.

@copperlight copperlight force-pushed the fix-time-error branch 2 times, most recently from ea83ac7 to 6dabf95 Compare May 29, 2024 03:04
We are trying to gather some data on the accuracy of clock time across the
fleet, and the `sys.time.estimatedError` was reporting a number of 16s values.

These values occur when the kernel has not synchonized the clock yet. This
fact is tracked with the `sys.time.unsynchronized` metric. The `estimatedError`
metric should only have valid results from `ntp_adjtime`.
@copperlight copperlight merged commit d40b66a into Netflix-Skunkworks:main May 29, 2024
2 checks passed
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.

1 participant