Beta system monitoring testing

I am testing a version 4 of the monitoring system on the beta system

It helps a lot to have more servers registered in the beta system: pool.ntp.org: the internet cluster of ntp servers

Some of you who have had servers in the beta system for a while will also have access to setup a monitoring agent:

1 Like

I recently registered some servers in the beta system, but when trying to validate am getting an error message when calling the https://validate6.ntppool.dev/b/ link:

default backend - 404

Else, I would have registered a few more servers by now (even though I am not eligible for a monitor at this time).

Also, user data download doesn’t work for me. It seems an archive is being generated. But when it is ready (apparently), there is no link next to the date/time string to actually download anything.

Lastly, the formatting on the site is strange: All links are underlined, the table underneath the offset/score graph lost its formatting.

1 Like

Another small thing I forgot: In the past, the “Client distribution” section would not show anything when a server had been in monitoring-only mode for long enough. Now, it is showing some data as if the server were actually in the pool with non-zero netspeed.

Fixed!

I think I’ve seen the underlined links for so long I got used to them (the beta site has been ahead of the production site git branch for a while!). :joy: Yeah, they do look weird!

In Safari the table underneath the graph looks okay, it just got smaller (which wasn’t intentional, fixing the CSS and HTML is not my favorite pastime). Which browser do you use? Can you share a screenshot?

The client distribution data comes from production; there’s only a production API for that. It’s a little confusing but better for testing than no data.

1 Like

Oh, and just a small question on my mind for a while: How does a client actually use the beta pool?

I’ve tried a few names I could come up with, but the right one wasn’t among them so far (i.e., they wouldn’t resolve).

ntp.beta.grundclock.com. It’s documented at pool.ntp.org: NTP Servers in All Pool Servers, ntp.beta.grundclock.com – Obviously using it outside a supervised test environment is probably a bad idea, so

Firefox and Chromium on Linux. Yeah, you are right. It is still visible as table, just without the colors, and the missing space makes it more difficult to read, for me at least.

Chromium:

Firefox:

Ah, I kind of suspected that… :slight_smile:

Ah, thanks. Now that you mention it, it is obvious… :face_with_diagonal_mouth: Thanks!

Just added a server too.
Happy to help out.
What are the changes in the beta monitoring system?

@Kets_One The new monitoring system supports v4 and v6 in one daemon and has a new API registration flow that’s much easier to use. (Also, new gRPC API internally, etc etc; it’s ~127 changes in git since I started the new version in late 2023!)

The goal is to have better support for more people running monitors, so another set of changes is to the “selector” that chooses the active monitor to help have the active monitors distributed across NTP Pool accounts, IP networks, etc.

git diff --stat says “168 files changed, 20126 insertions(+), 4285 deletions(-)” (though a bunch of that is generated and some LLM built design documents).

The code for the monitor is at GitHub - ntppool/monitor: monitoring agent for the NTP Pool

1 Like

Great to see this development in the monitoring backend!
Could you please share your plans for other changes aswell?
Many server owners are eager to see further adoption of IPv6.
Just wondering if that is in the plans for the near future.

1 Like

In the readme on the monitor github and some other places it is mentioned that the monitor client can be FreeBSD. Is there more info about that somewhere? The repo page also mention FreeBSD, but it looks like there are only linux packages.

hi @john1 – the system builds for FreeBSD, too, but only .tar.gz archives. There are URLs for the latest build here: https://builds.ntppool.dev/ntppool-agent/builds/test/475/checksums.txt (replace ‘checksum.txt’ with the filename).

This should have been fixed last night, too.

I checked a few times earlier today, no luck. But now it works. Thanks!!

.tar.gz is fine, thanks.

Just added my test server as well