Skip to content
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

Distribution value has |bucket_counts| fields that sum to 4 which does not equal the |count| field value of 2 #4868

Open
altunkan opened this issue Mar 22, 2024 · 3 comments

Comments

@altunkan
Copy link

Describe the bug
Hello,

Recently we have migrated our Spring Boot application from 2.7 to 3.2 and we've started to observe following error.

com.google.api.gax.rpc.InvalidArgumentException: io.grpc.StatusRuntimeException: INVALID_ARGUMENT: One or more TimeSeries could not be written: Field timeSeries[31].points[0].distributionValue had an invalid value: Distribution value has |bucket_counts| fields that sum to 4 which does not equal the |count| field value of 2.

Environment

  • Micrometer version: 1.12.2
  • Micrometer registry: Stackdriver
  • OS: Linux
  • Java version: 17

To Reproduce
How to reproduce the bug:

  private Timer buildDependencyTimer(DependencyTimer dependencyTimer) {
    return Timer.builder(LATENCY_DEPENDENCY_PREFIX)
        .tags(getDependencyTags(dependencyTimer))
        .publishPercentiles(percentiles)
        .publishPercentileHistogram()
        .minimumExpectedValue(Duration.ofNanos(1L))
        .register(meterRegistry);
  }

    dependencyLatencyTimers.putIfAbsent(dependencyTimer, buildDependencyTimer(dependencyTimer));
    dependencyLatencyTimers.get(dependencyTimer).record(responseTime, TimeUnit.MILLISECONDS);

Expected behavior
Metrics should be reported to stackdriver.

Additional context
Add any other context about the problem here, e.g. related issues.

@hudson155
Copy link

hudson155 commented Apr 6, 2024

Seeing the same thing on a new project @altunkan is this new after a version upgrade? I might try older versions...

@hudson155
Copy link

I got it working by downgrading to 1.11.6.

@altunkan
Copy link
Author

altunkan commented Apr 9, 2024

Yeah, I just tried with 1.11.6 by adding set('micrometer.version', '1.11.6') and looks like error is gone. Thank you! This will keep us good until micrometer team addresses the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants