[k8s] Promote a selection of container and k8s memory metrics to release_candidate#3883
Open
ChrsMark wants to merge 1 commit into
Open
[k8s] Promote a selection of container and k8s memory metrics to release_candidate#3883ChrsMark wants to merge 1 commit into
ChrsMark wants to merge 1 commit into
Conversation
dashpole
requested changes
Jul 13, 2026
dashpole
left a comment
Contributor
There was a problem hiding this comment.
Looks like some of these are the wrong instrument type.
7 tasks
Contributor
There was a problem hiding this comment.
Pull request overview
This PR promotes a specific set of Kubernetes and container memory metrics from development to release_candidate, reflecting their maturity and established usage in existing instrumentation (per issue #3882).
Changes:
- Promotes
*.memory.{usage,available,rss,working_set}metrics forcontainer,k8s.pod, andk8s.nodetorelease_candidate. - Expands/clarifies metric notes to describe semantics and derivation from Kubelet stats API (and cAdvisor for container metrics).
- Adds a changelog entry documenting the promotion.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
model/k8s/metrics.yaml |
Promotes selected k8s pod/node memory metrics to RC and clarifies *.memory.usage derivation/semantics. |
model/container/metrics.yaml |
Promotes selected container memory metrics to RC and expands notes (including cAdvisor + Kubelet derivation). |
docs/system/k8s-metrics.md |
Regenerates published k8s metrics docs to reflect RC status and updated notes. |
docs/system/container-metrics.md |
Regenerates published container metrics docs to reflect RC status and updated notes. |
.chloggen/rc_mem_metrics.yaml |
Adds release note entry for the RC promotion. |
…ase_candidate Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
Pull request dashboard statusStatus last refreshed: 2026-07-25 20:02:05 UTC.
This automated status or its linked feedback items may be incorrect. If something looks wrong, please report it with the result you expected. |
dashpole
approved these changes
Jul 23, 2026
lmolkova
approved these changes
Jul 23, 2026
jinja2
approved these changes
Jul 23, 2026
jsuereth
approved these changes
Jul 24, 2026
kamphaus
approved these changes
Jul 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #3882
After the evaluation described at #3882 (comment) I suggest we promote these metrics to
release_candidate.These have been in use from the https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/kubeletstatsreceiver/documentation.md for some time now without issues.
Changes
Please provide a brief description of the changes here.
Important
Pull request acceptance is subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above may be automatically rejected and closed.
Merge requirement checklist
Footnotes
Yes, I can answer maintainer questions about the content of this PR without using AI. ↩