Skip to content

New Blog Post: [collector] Announce the replacement of k8s utilization metrics #6847

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

Closed
ChrsMark opened this issue May 8, 2025 · 1 comment · Fixed by #6974
Closed

New Blog Post: [collector] Announce the replacement of k8s utilization metrics #6847

ChrsMark opened this issue May 8, 2025 · 1 comment · Fixed by #6974

Comments

@ChrsMark
Copy link
Member

ChrsMark commented May 8, 2025

The Opentelemetry Collector and specifically the kubeletstats receiver is going to replace/deprecate some previously enabled by-default metrics. The code-owners of the component would like to communicate this change with users beforehand so as to better prepare the ground for this change. Would a blog-post help with that?

ref: open-telemetry/opentelemetry-collector-contrib#39650 (comment)

This is part of a long ongoing effort: open-telemetry/opentelemetry-collector-contrib#27885

Title of the blog post: (Tentative) Announce the replacement of k8s utilization metrics

Content: (Will be relatively short) Explain the reason behind this change and how users will need to adopt their Collector installations

Related SIG: Collector SIG

/cc @TylerHelmuth @dmitryax @odubajDT

@svrnm
Copy link
Member

svrnm commented May 8, 2025

Yes, we can have a blog post for this, announcing breaking changes is always a good idea and we had those in the past already 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants