-
Notifications
You must be signed in to change notification settings - Fork 1k
Distribution value with |count| of 0 has a non-zero |mean| value
#5927
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
Comments
Hi @shakuzen , Sorry for the delay in getting back to you. We've released Any further suggestions gratefully received.
![]() |
@gruffT Looking at the changes made for this, to verify the fix, you need to use a snapshot version for the |
Yes, the fix was in micrometer-registry-stackdriver, but generally it is best to use a consistent version for all Micrometer dependencies in case the fix or other changes that may affect things working are across different modules. This can be done with the micrometer-bom or other forms of dependency management such as the dependency management offered by Spring Boot. You'll want to use that to override the version of all micrometer dependencies to e.g. 1.15.0-SNAPSHOT. Could you try that and let us know if you still see any issues? Thanks for the effort on this. It's appreciated. |
@gruffT Thank you for reporting the issue and testing the fix so quickly. The fix will be in the next round of releases. |
Distribution value with |count| of 0 has a non-zero |mean| value of XXX
errors in logs - similar to #4868Distribution value with |count| of 0 has a non-zero |mean| value
Describe the bug
We see a large number of error logs with the same message of form
Distribution value with |count| of 0 has a non-zero |mean| value of XXX
.I believe this is connected to #4868 which was recently resolved.
Environment
To Reproduce
How to reproduce the bug:
Expected behavior
No emit lots of error logs.
Additional context
Add any other context about the problem here, e.g. related issues.
Thank you for resolving #4868, I can confirm we saw those errors stop with application of the patch.
The text was updated successfully, but these errors were encountered: