mirror of
https://github.com/abh/ntppool.git
synced 2026-04-25 19:45:50 +03:00
[GH-ISSUE #228] Don't graph offsets when the server returned KoD #638
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntppool#638
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @abh on GitHub (Aug 12, 2023).
Original GitHub issue: https://github.com/abh/ntppool/issues/228
track in the monitor more explicitly that a kiss code was returned
don't use KoD offsets when graphing
(alternatively don't log the offset when a KissCode was returned)
https://community.ntppool.org/t/do-not-use-offset-value-from-kod-responses-in-offset-score-graphs/2988/
@hart-NTP commented on GitHub (Aug 13, 2023):
In a sense, a KoD RATE response is similar to a lack of response -- it provides no time information. In another sense, it's distinct, as it indicates there is a functioning NTP server responding in a timely, if useless, fashion.
Perhaps for scoring purposes it would make sense to treat a RATE response as a milder negative bump than a lack of response, and for offset graphing purposes, treat it similarly to a a non-response, that is, no offset data to graph.