-
Notifications
You must be signed in to change notification settings - Fork 181
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
Add system uptime metric #1507
Add system uptime metric #1507
Conversation
9566832
to
216bbf9
Compare
hi @kevinnoel-be! it may be worth looking over open-telemetry/oteps#185 |
216bbf9
to
b559797
Compare
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, this was pretty much what I was going to do. I do have an open question to semconv maintainers, depending on their answer may ask for a change or approve.
ded7632
to
474b5ab
Compare
Just want to call out that we have some previous thoughts and rationale here: open-telemetry/oteps#185 |
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.
Based on open-telemetry/oteps#185 and the response from the semconv maintainers, I'm requesting the following changes.
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.
As braydonk@ stated, I think the system.uptime
should be a gauge, which DOES deviate from other time-related values for specific reasons, which is why we wrote the OTEP oh so long ago.
Otherwise looks good.
474b5ab
to
f2f7dae
Compare
f2f7dae
to
5c286a9
Compare
Adressed all the comments, PTAL again, thanks! |
according to semantic convention, see discussion in: open-telemetry/semantic-conventions#1507
Fixes #648
Changes
Add
system.uptime
metricMerge requirement checklist