-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Metric] use Float64Counter to get wrong metric data #914
Comments
Hi, @nilebox I found that SDK reset the value of the counter when record's updateCount is not collectedCount, there is no any modification of collectedCount in code. so the value of the counter is reset. https://github.com/open-telemetry/opentelemetry-go/blob/master/sdk/metric/sdk.go#L376 opentelemetry-go/sdk/metric/sdk.go Line 437 in 27e892a
is it a bug? |
|
This is a case of open-telemetry/opentelemetry-collector#1255. The OTLP to Prometheus functionality is broken in the 0.4 collector release: we will disable the OTLP receiver in the 0.5 release and get this fixed in 0.6 I hope. |
Closing this as it's covered in collector issue 1255. |
Describe the bug
use Float64Counter to get the wrong metric data.
the code
the counter metric's value should not be reduced.
What did you expect to see?
the value of the counter keeps increasing by time.
What version did you use?
Version:
collector 0.5.0
otel: 0.7.0
What config did you use?
collector Config:
Environment
OS: macOS
Compiler: go version go1.14.2 darwin/amd64
Additional context
it works fine on version 0.3.0(collector) and otel(0.6.0).
The text was updated successfully, but these errors were encountered: