-
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
[k8sclusterreceiver] refactor metric units to follow Otel conventions #26708
[k8sclusterreceiver] refactor metric units to follow Otel conventions #26708
Conversation
gauge: | ||
value_type: int | ||
|
||
k8s.daemonset.current_scheduled_nodes: | ||
enabled: true | ||
description: Number of nodes that are running at least 1 daemon pod and are supposed to run the daemon pod | ||
unit: "1" | ||
unit: "{node}" |
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.
Not sure if this should be {node} or {pod} description says Number of nodes
. and metric name has current_scheduled_nodes
so went with nodes
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 node
is correct. For a given daemonset I believe this counts the number of nodes it is schedules on.
754dc45
to
8dba9f5
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
…open-telemetry#26708) **Description:** Refactor some metric units to follow OTEL Semantic conventions **Link to tracking Issue:** open-telemetry#10553
Description:
Refactor some metric units to follow OTEL Semantic conventions
Link to tracking Issue: #10553
Testing:
Documentation: