# Unreadable scale on the left Y axis of the monitoring graph (offset values)

**URL:** <https://community.ntppool.org/t/unreadable-scale-on-the-left-y-axis-of-the-monitoring-graph-offset-values/2804>\
**Category:** Pool Development\
**Tags:** monitoring\
**Created:** [March 24, 2023, 8:01am UTC](https://community.ntppool.org/t/unreadable-scale-on-the-left-y-axis-of-the-monitoring-graph-offset-values/2804 "2023-03-24T08:01:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![NTPman](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ntpman/32/450_2.png) [@NTPman](https://community.ntppool.org/u/NTPman)\
**Post date:** [March 24, 2023, 8:01am UTC](https://community.ntppool.org/t/unreadable-scale-on-the-left-y-axis-of-the-monitoring-graph-offset-values/2804/1 "2023-03-24T08:01:19Z")

</div>

> [@Monitoring upgrade](https://community.ntppool.org/t/monitoring-upgrade/2770/17):
>
> Yeah, your server appears to do so well in the monitoring that it’s breaking the graph! 😃

May be the opposite, when there is high offset value (one sample enough)?  
Let’s compare the two graphs:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/6/62cfc3beeb31b9a69007f31428293f411cfa597a.png)  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/1/148b1e1a2ccbf586267c56aa647f53eb87159cfd.png)  
The two servers are very similar. On the second image where the left side Y scaling is incorrect, the green dots are denser than on the first image. There is one bad offset sample, a red dot on the botom right side directly siting on the X axis. So the correct reading of the left Y axis would be: 0 ms, -100 ms, -200 ms … -700 ms.

---

<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:** [March 27, 2023, 4:06am UTC](https://community.ntppool.org/t/unreadable-scale-on-the-left-y-axis-of-the-monitoring-graph-offset-values/2804/2 "2023-03-27T04:06:46Z")

</div>

Yeah, I saw you pointed that out in the other thread and updated [the GitHub issue](https://github.com/abh/ntppool/issues/223). 🙂
