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

Don't graph offsets when the server returned KoD #228

Open
abh opened this issue Aug 12, 2023 · 1 comment
Open

Don't graph offsets when the server returned KoD #228

abh opened this issue Aug 12, 2023 · 1 comment

Comments

@abh
Copy link
Owner

abh commented Aug 12, 2023

  1. track in the monitor more explicitly that a kiss code was returned

  2. 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
Copy link

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.

abh added a commit to ntppool/monitor that referenced this issue Aug 14, 2023
- Score RATE responses as -3.5 instead of -5
- Turn off servers with DENY/RSTR responses (set score to -50)

abh/ntppool#228
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

No branches or pull requests

2 participants