-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/mysql]: add mysql.uptime metric #14747
[receiver/mysql]: add mysql.uptime metric #14747
Conversation
c1856ec
to
b5bfa0d
Compare
b5bfa0d
to
04d955e
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.
There appears to be a likely addition to the semantic conventions that would define uptime metrics. I think we should wait until that discussion is settled.
04d955e
to
cb286aa
Compare
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
This PR is closed already: open-telemetry/opentelemetry-specification#2824 |
It is closed, but is it resolved? |
In my opinion, at this point we should not wait any longer on adding this metric. Let's make a best effort for now. If necessary, we'll migrate to a new standard prior to declaring the component stable. The design here looks good to me, just need to rebase. |
cb286aa
to
c03fe3f
Compare
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
c03fe3f
to
0a30760
Compare
feat(mysqlreceiver): add mysql.uptime metric Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
Description:
add mysql.uptime metric
Link to tracking Issue:
#14138
Testing:
unit tests
Documentation:
metadata.yaml