-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Fix pprofile DurationNano to be a TypeUint64 #14188
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
Conversation
pcommon.Timestamp better represents a point in time rather than a duration. So keeping the proto field type for DurationNano is a better fit. Signed-off-by: Florian Lehner <[email protected]>
80184d1 to
7178c06
Compare
|
Could you also open the -contrib PR that fixes the tests there? |
Complementary change to open-telemetry/opentelemetry-collector#14188. Signed-off-by: Florian Lehner <[email protected]>
|
Signed-off-by: Florian Lehner <[email protected]>
Signed-off-by: Florian Lehner <[email protected]>
Signed-off-by: Florian Lehner <[email protected]>
Signed-off-by: Florian Lehner <[email protected]>
Signed-off-by: Florian Lehner <[email protected]>
Signed-off-by: Florian Lehner <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #14188 +/- ##
=======================================
Coverage 92.13% 92.14%
=======================================
Files 666 666
Lines 41438 41441 +3
=======================================
+ Hits 38180 38186 +6
+ Misses 2218 2216 -2
+ Partials 1040 1039 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Florian Lehner <[email protected]>
Signed-off-by: Florian Lehner <[email protected]>
| attribute.NewSet( | ||
| attribute.String(obsconsumer.ComponentOutcome, "success"), | ||
| ): 1186, | ||
| ): 1118, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my understanding, why did the numbers on this file changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If my understanding is correct, this number represents the size of pdata and with the change, pdata for profiling shrinked.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because it goes from a timestamp to an int.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, makes sense! Thanks
40c567e
|
open-telemetry/opentelemetry-collector-contrib/pull/44446 needs your help to address the deprecations |
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Complementary change to open-telemetry/opentelemetry-collector#14188. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Florian Lehner <[email protected]> Co-authored-by: Vihas Makwana <[email protected]> Co-authored-by: Pablo Baeyens <[email protected]>
#### Description The `Duration` and `SetDuration` methods were deprecated in #14188, and their implementations are now no-ops, causing [a benchmark to fail](https://github.com/open-telemetry/opentelemetry-collector/actions/runs/19668308741/job/56330560134). I updated the benchmark to use `DurationNano` and `SetDurationNano` instead.
Description
pcommon.Timestamp better represents a point in time rather than a duration. So keeping the proto field type for DurationNano is a better fit.
Corresponding Collector-contrib change: open-telemetry/opentelemetry-collector-contrib#44397
ping @open-telemetry/profiling-approvers
Link to tracking issue
Fixes #
Testing
Documentation