opentelemetry-dotnet
opentelemetry-dotnet copied to clipboard
Adding MinMax to Histograms
Fixes #2560
Changes
Histograms will now record the minimum and maximum measurement values.
For significant contributions please make sure you have completed the following items:
- [x] Appropriate
CHANGELOG.mdupdated for non-trivial changes - [ ] Design discussion issue #
- [x] Changes in public API reviewed
Codecov Report
Merging #2735 (a282844) into main (af7ab89) will decrease coverage by
0.42%. The diff coverage is76.59%.
Additional details and impacted files
@@ Coverage Diff @@
## main #2735 +/- ##
==========================================
- Coverage 87.35% 86.92% -0.43%
==========================================
Files 277 278 +1
Lines 10068 10151 +83
==========================================
+ Hits 8795 8824 +29
- Misses 1273 1327 +54
| Impacted Files | Coverage Δ | |
|---|---|---|
| ...ry/Metrics/ExplicitBucketHistogramConfiguration.cs | 83.33% <ø> (+22.22%) |
:arrow_up: |
| src/OpenTelemetry/Metrics/MetricPoint.cs | 75.00% <71.79%> (-8.00%) |
:arrow_down: |
| ...tryProtocol/Implementation/MetricItemExtensions.cs | 93.95% <100.00%> (+0.12%) |
:arrow_up: |
| src/OpenTelemetry/Metrics/HistogramBuckets.cs | 100.00% <100.00%> (ø) |
|
| ...rc/OpenTelemetry/Metrics/HistogramConfiguration.cs | 100.00% <100.00%> (ø) |
|
| src/OpenTelemetry/Metrics/Metric.cs | 95.50% <100.00%> (+1.12%) |
:arrow_up: |
| src/OpenTelemetry/Metrics/MetricReaderExt.cs | 86.36% <100.00%> (+1.81%) |
:arrow_up: |
| src/OpenTelemetry/Metrics/MetricStreamIdentity.cs | 90.62% <100.00%> (+0.62%) |
:arrow_up: |
| ...entation/ExportClient/OtlpGrpcTraceExportClient.cs | 35.71% <0.00%> (-42.86%) |
:arrow_down: |
| ...xporter.OpenTelemetryProtocol/OtlpTraceExporter.cs | 36.36% <0.00%> (-40.91%) |
:arrow_down: |
| ... and 14 more |
https://github.com/open-telemetry/opentelemetry-dotnet/pull/2718 changes the layout, so this will be affected.
https://github.com/open-telemetry/opentelemetry-dotnet/pull/2705/files - need to bring this back as well. (it was reverted)
https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry/Metrics/MetricType.cs also see this class.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
Closed as inactive. Feel free to reopen if this PR is still being worked on.
Could this be reopened please :)
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day.
Comment to keep this open. I'm excited and eager to see this changed merged and released.
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day.
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day.
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day.
Closed as inactive. Feel free to reopen if this PR is still being worked on.
Can this be reopened? Is it being worked on?
@mic-max Please resolve the merge conflicts for getting this PR ready for review.
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day.
Would love to have this. For me, I'm recording queue processing times and having the average is alright, but what I really want to know is what the max time is.
I guess there wouldn't be any way to get something like the 99th percentile from a histogram even with this change. I was reading docs on OpenTelemetry specs and it seems like doing percentiles isn't really going to be supported.
I guess there wouldn't be any way to get something like the 99th percentile from a histogram even with this change. I was reading docs on OpenTelemetry specs and it seems like doing percentiles isn't really going to be supported.
Histogram exports buckets, allowing backends to calculate percentiles.
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day.
Do we need help getting this completed and merged? It seems like an important feature for otel metrics.
Let me know when you want to merge this and I will resolve the conflicts, not going to waste my time fixing preemptively just for new conflicts to come up
The PR looks good except for 2 things:
- MinMwx should be part of Identity. Must be fixed in this PR.
- Other exporters will break with this change. The fix is in other exporters, but blocking PR to prevent accidental merge until exporters are hotfixed. See https://github.com/open-telemetry/opentelemetry-dotnet/pull/2735/files#r989476122
if we keep the metric type same, then it wont break existing exporters. and can use Nan/Infinity to indicate lack of min/max
Merging. @alanwest please take a final look and share any issues you see!