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.

Sign up for GitHub

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

Jump to bottom

Cumulative Counters - Prometheus receiver- Magnitude of the metrics is lost #289

Closed
vishiy opened this issue Mar 30, 2021 · 2 comments · Fixed by #295
Closed

Cumulative Counters - Prometheus receiver- Magnitude of the metrics is lost #289

vishiy opened this issue Mar 30, 2021 · 2 comments · Fixed by #295

Comments

@vishiy
Copy link

vishiy commented Mar 30, 2021 •
edited
Loading

In using prometheus receiver, i see prometheus counters are being re-calculated from the first data point, which loses the actual value/magnitude of the metric. Is there a way to pass on the initial value in the pipeline so that it can be added back before ingesting to backends like prometheus ?
@vishiy
Copy link
Author

vishiy commented Mar 30, 2021

#229

@jsuereth jsuereth mentioned this issue Apr 20, 2021
Closed
@jsuereth
Copy link
Contributor

We had a heavy discussion on this in the data-model SiG today.

TL;DR: @jmacd has a proposal where we pass the FIRST value as-is. I think we can use this bug to expand on tracking tthat functionality in addition to a real implementation in #2852

This was referenced Apr 22, 2021
Merged
Merged
@vishiy vishiy mentioned this issue Aug 30, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add comments about StartTimeUnixNano jmacd/opentelemetry-proto
2 participants
@jsuereth @vishiy