-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support float ping value #3345
Comments
Why is the difference between 1..2ms important to you? |
I monitor sites on the same server as UK is running on, so it's not 10ms but 1-2ms. This is not useful to differentiate and creates a very jagged graph. |
@Potat0000 #3987 was merged and relased in |
This is not fixed, I'm using 1.23.7 and HTTP is still rounded to int. |
Thank you to all of you who are still following this issue. It can be confirmed that in 1.23.7 push type can store float value again. Since my original request is to support float ping value for push type, I think this issue could close as completed. You can open another issue to ask for float values for other types like HTTP. |
🏷️ Feature Request Type
Other
🔖 Feature description
In #3343 and #3320 , I said that I'm using the ping field to record the latency to the gateway. Obviously a float type data is very necessary in this case because all the latency data is between 1ms and 2ms. This feature may have been implemented by mistake since in version 1.21 and earlier, it could record ping values with float type and the graph below can also display the float type graph very well.
✔️ Solution
Supporting float ping value for push type and even for other type (for Response field).
❓ Alternatives
No response
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: