# Beta site changes - monitoring updates

**URL:** <https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659>\
**Category:** Pool Development\
**Tags:** monitoring, beta\
**Created:** [August 19, 2017, 9:28am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659 "2017-08-19T09:28:26Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [August 19, 2017, 9:28am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/1 "2017-08-19T09:28:26Z")

</div>

Hi everyone,

I’ve been working on making most of the NTP Pool server components run under Kubernetes to make it easier to manage and continue to extend (for a particular flavor of “easier”, of course). The beta system is running on [https://web.beta.grundclock.com/](https://web.beta.grundclock.com/) (separate NTP Pool database, but same login system and login accounts as the regular site).

I have a bunch of upcoming changes to improve the monitoring system – better availability of long-term monitoring data and better support for multiple monitoring servers.

It’s helpful to me to have more servers registered in the beta system, so please consider adding your server at [https://manage-beta.grundclock.com/manage](https://manage-beta.grundclock.com/manage)🙂

---

<div class="post-metadata">

**Author:** ![HansMayer](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/hansmayer/32/95_2.png) [@HansMayer](https://community.ntppool.org/u/HansMayer)\
**Post date:** [August 23, 2017, 6:51pm UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/2 "2017-08-23T18:51:53Z")

</div>

I add some stratum 2 server but there is no statistics available.  
So I believe it will start later if you ave more stations.

// Hans

---

<div class="post-metadata">

**Author:** ![ebahapo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ebahapo/32/1152_2.png) [@ebahapo](https://community.ntppool.org/u/ebahapo)\
**Post date:** [August 26, 2017, 5:48pm UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/3 "2017-08-26T17:48:15Z")

</div>

I see that there are monitoring stations in LA, Hollywood and LU. What are their IPv4 and IPv6 prefixes so that I can note them in my logs, please?

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/mnordhoff/32/1470_2.png) [@mnordhoff](https://community.ntppool.org/u/mnordhoff)\
**Post date:** [August 28, 2017, 2:15am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/4 "2017-08-28T02:15:55Z")

</div>

Is beta monitoring currently running? Should it be?

[https://web.beta.grundclock.com/user/mnordhoff](https://web.beta.grundclock.com/user/mnordhoff) shows, uh, not much activity.

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [August 28, 2017, 7:46am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/5 "2017-08-28T07:46:30Z")

</div>

Whoops. I made the beta site “TLS-only” but didn’t fix the monitoring client to load the CA-roots to validate the certificate. I will fix it Monday evening.

---

<div class="post-metadata">

**Author:** ![HansMayer](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/hansmayer/32/95_2.png) [@HansMayer](https://community.ntppool.org/u/HansMayer)\
**Post date:** [August 30, 2017, 6:08pm UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/6 "2017-08-30T18:08:00Z")

</div>

Hi Ask,

there are still no data.  
[https://web.beta.grundclock.com/user/6476i5cd3footcjg3hpo](https://web.beta.grundclock.com/user/6476i5cd3footcjg3hpo)

Kind regards  
Hans

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [September 5, 2017, 7:31am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/7 "2017-09-05T07:31:21Z")

</div>

The deployment of the monitor code didn’t like that the site forced TLS.

The easy fix for that meant some changes that could impact the production site, too, so instead I rewrote the monitor in Go. This will allow it to more easily also do traceroutes and do more checks per hour, so hopefully it’ll be worth a few days of no monitoring on the beta site. 🙂

It’s running on the same server as the production monitor, so I’m interested in any difference in the monitoring results between the monitoring on the production site and the beta site.

---

<div class="post-metadata">

**Author:** ![avij](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/avij/32/197_2.png) [@avij](https://community.ntppool.org/u/avij)\
**Post date:** [October 27, 2017, 12:15am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/8 "2017-10-27T00:15:35Z")

</div>

Hey guys, I think it would be helpful to have more NTP servers from around the world on the beta site to test the monitoring changes. For example, there are only 5 IPv4 and 5 IPv6 servers (presumably the same servers) in the entire Asia beta zone. So please add your servers to the beta pool to give Ask some more testing data. I have all my 4 NTP servers (all dual-stack) there already.

---

<div class="post-metadata">

**Author:** ![zorko](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/zorko/32/64_2.png) [@zorko](https://community.ntppool.org/u/zorko)\
**Post date:** [November 2, 2017, 2:38pm UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/9 "2017-11-02T14:38:17Z")

</div>

I just added my 5 servers in Croatia.

---

<div class="post-metadata">

**Author:** ![zorko](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/zorko/32/64_2.png) [@zorko](https://community.ntppool.org/u/zorko)\
**Post date:** [November 2, 2017, 2:40pm UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/10 "2017-11-02T14:40:47Z")

</div>

PS: Why did I get such a strange user name (some unpronoucable and unmemorisable string of letters and numbers)?

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [November 3, 2017, 6:09am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/11 "2017-11-03T06:09:29Z")

</div>

The previous login system provided a unique username, so it used to be that. The new login system just uses email addresses, and I don’t want to use those for obvious reasons.

There really should be a way to edit the username or better to edit a “what to be called” field on the site (name, organization name, pseudonym, …) and then use something random looking for the URLs. It’s somewhere on the todo.

---

<div class="post-metadata">

**Author:** ![avij](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/avij/32/197_2.png) [@avij](https://community.ntppool.org/u/avij)\
**Post date:** [December 18, 2017, 9:58pm UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/12 "2017-12-18T21:58:22Z")

</div>

> [@ask](#):
>
> It’s running on the same server as the production monitor, so I’m interested in any difference in the monitoring results between the monitoring on the production site and the beta site.

[http://www.pool.ntp.org/scores/173.255.246.13](http://www.pool.ntp.org/scores/173.255.246.13) and [https://web.beta.grundclock.com/scores/173.255.246.13](https://web.beta.grundclock.com/scores/173.255.246.13) look a bit different, even after taking into account that the time scales are different. Here are some screen captures for posterity (production and beta, respectively):  
 ![ntpprod](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/1X/05ee8625b3ce744ed55389d15cca961c4061211b.png)  
 ![ntpbeta](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/1X/95eec6b07815a266c090eba142704600fe8e4e7b.png)  
This server is hosted at Linode and they claim that the reason for the dropped packets is that I sometimes exceed 30000 outbound packets per second on that server. I’m not quite sure if that’s true, but I’m investigating further. My other NTP servers are doing fine.

---

<div class="post-metadata">

**Author:** ![hahnro](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/hahnro/32/27_2.png) [@hahnro](https://community.ntppool.org/u/hahnro)\
**Post date:** [January 2, 2018, 4:40pm UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/13 "2018-01-02T16:40:21Z")

</div>

Hi Ask, I just extended the deletion date of my server (89.101.218.6 - Ireland) to April 2018 - I’m curious what provider the site in Luxembourg is on. I’m still with Virgin Media business fibre and seeing a consistent score of -5 with this LU site. The US scores are horrible and have been for about 1 year now. Never did get to the bottom of the monitoring issue.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/1X/4b6d045f93c7f5ee7893452d24638b3bcde64078.png)

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [January 22, 2018, 9:00am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/14 "2018-01-22T09:00:34Z")

</div>

The Luxembourg and Hollywood monitors aren’t running.

The system needs a feature to mark the monitors as inactive (and not show them unless there’s data from that monitor on the chart?).

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [February 10, 2018, 10:12am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/15 "2018-02-10T10:12:10Z")

</div>

The new monitors are going – [Beta system now has multiple monitors](https://community.ntppool.org/t/beta-system-now-has-multiple-monitors/726)

---

<div class="post-metadata">

**Author:** ![iocc](https://avatars.discourse-cdn.com/v4/letter/i/ba9def/32.png) [@iocc](https://community.ntppool.org/u/iocc)\
**Post date:** [February 18, 2018, 3:32pm UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/16 "2018-02-18T15:32:17Z")

</div>

Not possible to add servers to [https://manage-beta.grundclock.com/](https://manage-beta.grundclock.com/),  
it just says “Could not check NTP status” when I try to add them.

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [February 20, 2018, 1:56am UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/17 "2018-02-20T01:56:46Z")

</div>

What was the IP? (Send it privately if more appropriate). The only errors I see in the logs were for an IP that timed out on the NTP request (and it looks like that bubbles up to the web UI weirdly).

---

<div class="post-metadata">

**Author:** ![iocc](https://avatars.discourse-cdn.com/v4/letter/i/ba9def/32.png) [@iocc](https://community.ntppool.org/u/iocc)\
**Post date:** [May 4, 2018, 12:45pm UTC](https://community.ntppool.org/t/beta-site-changes-monitoring-updates/659/18 "2018-05-04T12:45:33Z")

</div>

I was trying to add ntp1,ntp2,ntp5,ntp6,ntp7,ntp8.flashdance.cx that have these IPs:

[http://www.pool.ntp.org/scores/193.228.143.12](http://www.pool.ntp.org/scores/193.228.143.12)  
[http://www.pool.ntp.org/scores/193.228.143.13](http://www.pool.ntp.org/scores/193.228.143.13)  
[http://www.pool.ntp.org/scores/193.228.143.14](http://www.pool.ntp.org/scores/193.228.143.14)  
[http://www.pool.ntp.org/scores/193.228.143.22](http://www.pool.ntp.org/scores/193.228.143.22)  
[http://www.pool.ntp.org/scores/193.228.143.23](http://www.pool.ntp.org/scores/193.228.143.23)  
[http://www.pool.ntp.org/scores/193.228.143.24](http://www.pool.ntp.org/scores/193.228.143.24)
