Skip to content

Refactor and Log NTP drift measurements to a local CSV file#1

Merged
borland merged 4 commits into
mainfrom
orion/refactor-and-logging
Jun 9, 2026
Merged

Refactor and Log NTP drift measurements to a local CSV file#1
borland merged 4 commits into
mainfrom
orion/refactor-and-logging

Conversation

@borland

@borland borland commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator

Now logs drift measurements to a local CSV file so they can be scooped up into a TeamCity artifact, rather than needing to go look in sumo for the windows event logs

@borland borland changed the title Refactor and Logging Refactor and Log NTP drift measurements to a local CSV file Jun 4, 2026
Comment thread plot_drift.py
@@ -0,0 +1,97 @@
#!/usr/bin/env python3

@YuKitsune YuKitsune Jun 8, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this necessary?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the pet script that claude wrote for me to draw a png file based on ntp-drift.csv. The output looks like this:
ntp-drift

It's useful to keep, so we can have a deterministic way of making graphs (rather than asking claude to do it each time), so I saved the script here, even though it's not directly related to the time service.

If you're referring specifically to whether the #!/usr/bin/env python3 line, no, it isn't neccessary, you can run python3 plot_drift.py with or without it. But it's a very common/standard thing for scripts on unix, many python scripts have it, so it seemed fine to me

@borland borland merged commit c155399 into main Jun 9, 2026
2 checks passed
@borland borland deleted the orion/refactor-and-logging branch June 9, 2026 01:29
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