Add k8s resourcequota metrics#2113
Conversation
fc1f9e0 to
c3d0534
Compare
c3d0534 to
3a0e762
Compare
rogercoll
left a comment
There was a problem hiding this comment.
Are those metrics specific per k8s namespace? Should we add the k8s.namespace.name attribute?
The min requirement is In any case we will need to revisit this as part of #1421. For the records, today the Collector reports the namespace as well: Resource attributes:
-> k8s.resourcequota.uid: Str(31c6317a-d8d4-48ea-adb0-e35074818623)
-> k8s.resourcequota.name: Str(mem-cpu-demo)
-> k8s.namespace.name: Str(default)(ref) |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
Still valid, waiting for #2076.. |
7b69824 to
3ed2067
Compare
3efbe70 to
e3c20fb
Compare
|
@jinja2 @dmitryax I have updated this PR based on #2076 (comment). Please take a look when you find the time. Thank's! |
62032b3 to
c737467
Compare
Signed-off-by: ChrsMark <[email protected]>
e90dd04 to
f776b08
Compare
Signed-off-by: ChrsMark <[email protected]>
2226e8d to
a31fd3d
Compare
Signed-off-by: ChrsMark <[email protected]>
Signed-off-by: ChrsMark <[email protected]>
|
This one has already 2 approvals from K8s SIG. @open-telemetry/specs-semconv-approvers @open-telemetry/specs-semconv-maintainers feel free to take a look :) |
Signed-off-by: ChrsMark <[email protected]>
Signed-off-by: ChrsMark <[email protected]>
Signed-off-by: ChrsMark <[email protected]>
Signed-off-by: ChrsMark <[email protected]>
Fixes #2076
Changes
This PR introduces the following metrics as part of #1032:
This addition follows the K8s spec and compute docs:
Is aligned with the respective Resource Attributes:
semantic-conventions/model/k8s/resources.yaml
Line 135 in 0c0b799
Merge requirement checklist
[chore]Extra context
A
ResourceQuotaobject will come with astatuslike the following:(ref)
Collector implementation reference: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/9bb671ca7ab3a9e0861d068f15b146aaa55766c2/receiver/k8sclusterreceiver/documentation.md?plain=1#L271-L291. Note that this PR does not follow the schema that the existing implementation follows (see #2076 (comment)).