-
Notifications
You must be signed in to change notification settings - Fork 27
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
CPU runtime and timing metrics #269
Conversation
Codecov ReportBase: 93.64% // Head: 93.38% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #269 +/- ##
==========================================
- Coverage 93.64% 93.38% -0.27%
==========================================
Files 68 69 +1
Lines 3669 3749 +80
==========================================
+ Hits 3436 3501 +65
- Misses 181 190 +9
- Partials 52 58 +6
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
LGTM!
Co-authored-by: Gustavo Paiva <guustavo.paiva@gmail.com>
… into jmacd/cputime
FYI @paivagustavo I created |
Description:
Produces process.cpu.time metrics, formerly produced by the go-contrib instrumentation/host package. This is not host instrumentation, could become runtime instrumentation.
runtime.uptime
metric from go-contrib's instrumentation/runtime that would ideally become aruntime/metric
consistent with the next,runtime/metric
.See also Runtime instrumentation: GC "total time spent" metric open-telemetry/opentelemetry-go-contrib#316.
Part of #257. Part of #270.
Link to tracking Issue:
Testing: < Describe what testing was performed and which tests were added.>
Documentation: < Describe the documentation added.>