-
Notifications
You must be signed in to change notification settings - Fork 139
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 node.js runtime metrics semantic conventions #991
base: main
Are you sure you want to change the base?
Conversation
0415b17
to
8b98001
Compare
I wasn't sure if I need to update something on the next, since there was no changes to existing semantic. This is a new one. |
cc @open-telemetry/javascript-approvers |
e103e60
to
42c6ce3
Compare
I am wondering whether or not it should be called NodeJS. What if someone uses Deno or Bun? |
50b741f
to
5eb9c53
Compare
what about just |
I mean I guess, but also feel like it can be confused with the language instead of the runtime environment |
if we want to go be definition, it would be |
jsruntime sounds maybe better? idk, might need some extra opinions |
12a8c9f
to
ce06636
Compare
.chloggen/jsruntime-metrics.yaml
Outdated
component: jsruntime | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Introducing semantic conventions for Runtime Javascript (e.g. NodeJS, DenoJS, BunJS) runtime metrics. |
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.
I don't believe Deno and Bun use the JS suffix
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.
removed
For my opinion different runtimes need to have diferent preffix. Also i think for version we need to set metric like it does in the prom-client library. Attribute in all metrics with version, for my opinion, it's not a good solution. |
… into nodejs-metrics
… into nodejs-metrics
New updates:
|
<!-- semconv metric.veightjsengineruntime.memory.size(metric_table) --> | ||
| Name | Instrument Type | Unit (UCUM) | Description | Stability | | ||
| -------- | --------------- | ----------- | -------------- | --------- | | ||
| `v8jsengineruntime.memory.size` | UpDownCounter | `By` | External memory size. | ![Experimental](https://img.shields.io/badge/-experimental-blue) | |
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.
I think it's Gauge. like in prom-client library
From the discussion on the SIG meeting, keeping this PR just for node and created a new one for the v8 on #1066 |
docs/attributes-registry/nodejs.md
Outdated
|
||
## NodeJS Attributes | ||
|
||
Describes Node.js Runtime related attributes. |
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.
are those always only runtime attributes? I wonder if registry as agnostic entity should have runtime
word
Describes Node.js Runtime related attributes. | |
Describes Node.js related attributes. |
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.
good point, removed!
Part Of #990
Changes
Adding semantic conventions for Node.js runtime metrics
Merge requirement checklist
[chore]