Export internal metrics to follow dot notation#1147
Export internal metrics to follow dot notation#1147christos68k merged 19 commits intoopen-telemetry:mainfrom
Conversation
| }, | ||
| { | ||
| "description": "Number of failures to read from pyinfo->pyThreadStateCurrentAddr", | ||
| "description": "Number of failures to read from pyinfo-\u003epyThreadStateCurrentAddr", |
There was a problem hiding this comment.
Can we revert these changes to \u003e?
32ac664 to
c8522a5
Compare
c8522a5 to
db9ed11
Compare
| "type": "counter", | ||
| "name": "Invalid", | ||
| "field": "", | ||
| "field": "invalid", |
There was a problem hiding this comment.
We don't need to set this, it'll never be sent and it's confusing if we give it a field value
| "field": "invalid", | |
| "field": "", |
There was a problem hiding this comment.
@christos68k after adding validation that field can't be empty this is not valid and initilization panics
do you think we should keep it as "invalid"?
rogercoll
left a comment
There was a problem hiding this comment.
The metric field names in metrics/metrics.json are mostly well-structured, but have several areas of non-compliance with the OpenTelemetry Semantic Convention naming guidelines (https://opentelemetry.io/docs/specs/semconv/general/naming/) and metrics conventions (https://opentelemetry.io/docs/specs/semconv/general/metrics/).
I agree on merging this PR, but I would suggest not using semantic conventions as commit message. Instead: Export internal metrics to follow dot notation.
This PR corresponds to the first task to migrate to OpenTelemetry naming, see #1115 (comment)
|
@NimrodAvni78 Can you address the latest round of comments so that we can move forward with this PR? Thanks! |
Co-authored-by: Roger Coll <roger.coll@elastic.co>
Co-authored-by: Roger Coll <roger.coll@elastic.co>
Co-authored-by: Roger Coll <roger.coll@elastic.co>
Co-authored-by: Roger Coll <roger.coll@elastic.co>
Co-authored-by: Roger Coll <roger.coll@elastic.co>
done 👌. @rogercoll do you want to to also change the issue name? or change the description of this PR to not close the issue? |
|
@christos68k just merged all suggestions. so should be good to go |
Thanks @NimrodAvni78 , no worries, we can keep the issue as is and re-open it afterwards. |
|
@christos68k @rogercoll do you think this could get merged? |
Hi @NimrodAvni78, there are a few comments you haven't addressed, once you do we can merge this PR. |
Co-authored-by: Florian Lehner <florianl@users.noreply.github.com>
Co-authored-by: Christos Kalkanis <christos.kalkanis@elastic.co>
Co-authored-by: Christos Kalkanis <christos.kalkanis@elastic.co>
resolves #1115