# Monitoring metrics

**URL:** <https://community.ntppool.org/t/monitoring-metrics/4003>\
**Category:** Monitoring Operators\
**Tags:** monitoring\
**Created:** [August 4, 2025, 4:32am UTC](https://community.ntppool.org/t/monitoring-metrics/4003 "2025-08-04T04:32:09Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![john1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/john1/32/1464_2.png) [@john1](https://community.ntppool.org/u/john1)\
**Post date:** [August 4, 2025, 4:32am UTC](https://community.ntppool.org/t/monitoring-metrics/4003/1 "2025-08-04T04:32:09Z")

</div>

How are the totals in the light blue calculated? I have only the two monitors and if I add their reported 1 hour tests/min, I get 13.1 + 9.6 = 22.7, which is roughly half of what is reported in the blue block. The 24 hour rate in blue is also roughly double. Is it because the monitors have both IPv4 and IPv6 addresses?

 ![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/c/cd36a802524697475dc127d4422b9c7847fa732c.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:** [August 4, 2025, 4:09pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/2 "2025-08-04T16:09:45Z")

</div>

I moved this from the “mega thread” so it wouldn’t get lost.

The metrics are from prometheus, and yes – something is definitely off!

---

<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 4, 2025, 5:00pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/3 "2025-08-04T17:00:06Z")

</div>

2 posts were merged into an existing topic: [“monitor=recentmedian” no longer works](https://community.ntppool.org/t/monitor-recentmedian-no-longer-works/4002/3)

---

<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 5, 2025, 4:18am UTC](https://community.ntppool.org/t/monitoring-metrics/4003/4 "2025-08-05T04:18:49Z")

</div>

This has been fixed!

---

<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 5, 2025, 2:39pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/5 "2025-08-05T14:39:22Z")

</div>

No, it doesn’t seem to have been fixed. It’s still showing exactly double.

---

<div class="post-metadata">

**Author:** ![apuls](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/apuls/32/1467_2.png) [@apuls](https://community.ntppool.org/u/apuls)\
**Post date:** [August 5, 2025, 9:17pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/6 "2025-08-05T21:17:53Z")

</div>

“My Stats” are correct. The sum of all monitors is equal with the one from the blue banner.

---

<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 6, 2025, 3:08am UTC](https://community.ntppool.org/t/monitoring-metrics/4003/7 "2025-08-06T03:08:50Z")

</div>

You are both right, I think! Some of the accounts are still showing the double counts. 🤔

---

<div class="post-metadata">

**Author:** ![john1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/john1/32/1464_2.png) [@john1](https://community.ntppool.org/u/john1)\
**Post date:** [August 6, 2025, 3:32am UTC](https://community.ntppool.org/t/monitoring-metrics/4003/8 "2025-08-06T03:32:29Z")

</div>

Both the production and beta sites still show double the sum in blue for me. All my monitors are registered for both IPv4 and IPv6.

---

<div class="post-metadata">

**Author:** ![john1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/john1/32/1464_2.png) [@john1](https://community.ntppool.org/u/john1)\
**Post date:** [August 8, 2025, 6:43am UTC](https://community.ntppool.org/t/monitoring-metrics/4003/9 "2025-08-08T06:43:55Z")

</div>

I see the values for ok, timeout and offset disappeared on both the beta and prod systems?

![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/7/798cd9eee28899cf5b53fa8a1e4014804245af3e.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:** [August 8, 2025, 7:19am UTC](https://community.ntppool.org/t/monitoring-metrics/4003/10 "2025-08-08T07:19:20Z")

</div>

> [@john1](#):
>
> Both the production and beta sites still show double the sum in blue for me. All my monitors are registered for both IPv4 and IPv6.

🤯 Right this moment it looks okay in your account; your two monitors numbers add up to the total in blue.

The ok/timeout/offset box is supposed to show how many results of the various kinds, but only if they are more than 0 (and it’s not even showing 0, so that’s not the bug). That feature looks completely broken, I’ll have a look later. Maybe I lost track of what bugs I was fixing and pushed an update to the website but not the API behind Sunday evening. I haven’t touched the production site all week.

---

<div class="post-metadata">

**Author:** ![john1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/john1/32/1464_2.png) [@john1](https://community.ntppool.org/u/john1)\
**Post date:** [August 8, 2025, 7:32am UTC](https://community.ntppool.org/t/monitoring-metrics/4003/11 "2025-08-08T07:32:21Z")

</div>

Is it possible that it can show different for different people? Even after a reload of the page, I still see double:

![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/e/e313195c192946c6b13520fb5d318c481767f731.png)

##### zakim1-yfhw4a and zawkf1-yfhw4a

![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/9/9d73f6ccbf9424b75fa62b929b75c99a824193fc.png) ![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/1/134798e32f63d59eb33271d8babfa84b49a4187a.png)

---

<div class="post-metadata">

**Author:** ![john1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/john1/32/1464_2.png) [@john1](https://community.ntppool.org/u/john1)\
**Post date:** [August 10, 2025, 2:44pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/12 "2025-08-10T14:44:31Z")

</div>

I see the totals are not double anymore and the ok, timeout and offset fields have numbers again. Thank you!

![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/0/0e6e582687edaeff9fb64c3f2a91aa2d86ca2db4.png)

---

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [August 10, 2025, 4:46pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/13 "2025-08-10T16:46:20Z")

</div>

> [@john1](#):
>
> the ok, timeout and offset fields have numbers again.

> [@john1](#):
>
> Is it possible that it can show different for different people?

At least my dashboard _currently_ is still missing the ok/timeout/offset breakdown numbers.

 ![Screenshot_20250810-184304_Ecosia](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/3/36a0a592b25e85b88a9850a8dc915f11c5bbda54.jpeg)

---

<div class="post-metadata">

**Author:** ![john1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/john1/32/1464_2.png) [@john1](https://community.ntppool.org/u/john1)\
**Post date:** [August 10, 2025, 5:20pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/14 "2025-08-10T17:20:26Z")

</div>

It was fixed on the beta site for me. I think it has not been rolled out to the production side yet.

---

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [August 10, 2025, 5:54pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/15 "2025-08-10T17:54:17Z")

</div>

Ah, ok, sorry. Since the rollout of the new monitoring to the production site, I admittedly haven’t paid much attention to beta anymore, also given issues in adding new monitors there (which Ask is possibly going to look into later today). I.e., I don’t know what the situation was in the interim, but now looking good wrt ok/timeout/offset on beta:

![Screenshot from 2025-08-10 19-53-21](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/5/53ece425f5d4ac7ab670f8248bba40dfb6bb64b0.png)

---

<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 11, 2025, 7:33pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/16 "2025-08-11T19:33:17Z")

</div>

![Captura de Tela 2025-08-11 às 16.31.59](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/a/a8d70ef61b370ad96d747b18cf2aeb407c8b65db.png)

Rates doubled, no breakdown numbers for me.

---

<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 11, 2025, 11:17pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/17 "2025-08-11T23:17:29Z")

</div>

I’ve updated the production site.

---

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [August 12, 2025, 8:46pm UTC](https://community.ntppool.org/t/monitoring-metrics/4003/19 "2025-08-12T20:46:13Z")

</div>

The quorum mechanism now seems to no longer allow a single monitor above the threshold to supersede _all_ other monitors below the threshold. At least in the situation shown below:

 ![Screenshot_20250812-224122_Ecosia](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/3/320127175de28167a37b00a3fbd2cf843fad4b56.jpeg)

---

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [August 13, 2025, 7:22am UTC](https://community.ntppool.org/t/monitoring-metrics/4003/21 "2025-08-13T07:22:30Z")

</div>

> [@MagicNTP](#):
>
> quorum mechanism now seems to no longer allow a single monitor above the threshold to supersede _all_ other monitors below the threshold

I am sorry that conclusion seems to have been premature:

 ![Screenshot_20250813-091932_Ecosia](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/9/90e10f3b5bb44f8052534c5bc4af0dd5104c7fe4.jpeg)
