Skip to content

Conversation

@beanliu
Copy link
Contributor

@beanliu beanliu commented Jan 25, 2021

follow up PR of #2581

  • implement histogram aggregation export in OTLP.

@codecov
Copy link

codecov bot commented Jan 25, 2021

Codecov Report

Merging #2582 (a6326f1) into main (f1c38ef) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@     Coverage Diff      @@
##   main   #2582   +/-   ##
============================
============================

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f1c38ef...60d0f85. Read the comment docs.

Base automatically changed from master to main January 26, 2021 00:26
@bogdandrutu
Copy link
Member

bogdandrutu commented Feb 25, 2021

Please rebase, I think this can be merged/finished before the aggregator PR (if ready) :)

@beanliu
Copy link
Contributor Author

beanliu commented Feb 26, 2021

the PR has been rebased and updated according to the latest changes.

Comment on lines +247 to +250
List<Double> boundaries = doubleHistogramPoint.getBoundaries();
if (!boundaries.isEmpty()) {
builder.addAllExplicitBounds(boundaries);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Counts as well. So we add boundaries and counts if boundaries not empty, otherwise the counts will be a list with one long equivalent with count.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

counts will be a list with one long equivalent with count.

that looks like a valid OTLP histogram point to me according to https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/metrics/v1/metrics.proto#L428.

boundaries and counts both being empty might be a problem to the downstream consumers since it's not in the contract.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment is written with the mindset that there will be more options to define the boundaries like linear or exponential

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure if I follow. seems to me that the minimal size of buckets should be one according to https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/metrics/v1/metrics.proto#L414

// The number of elements in bucket_counts array must be by one greater than
// the number of elements in explicit_bounds array.

and the service we built treats histogram data points without buckets invalid.

Copy link
Contributor

@jkwatson jkwatson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@jkwatson jkwatson merged commit 02ca7c2 into open-telemetry:main Mar 1, 2021
This was referenced Dec 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants