Skip to content
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

[receiver/kubeletstatsreceiver] update scope name for consistency #34537

Conversation

codeboten
Copy link
Contributor

Update the scope name for telemetry produced by the kubeletstatsreceiverreceiver from otelcol/kubeletstatsreceiver to github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kubeletstatsreceiverreceiver

Part of open-telemetry/opentelemetry-collector#9494

Update the scope name for telemetry produced by the kubeletstatsreceiverreceiver from otelcol/kubeletstatsreceiver to github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kubeletstatsreceiverreceiver

Part of open-telemetry/opentelemetry-collector#9494

Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
@codeboten codeboten requested a review from a team August 8, 2024 18:36
@codeboten codeboten merged commit 23ccb80 into open-telemetry:main Aug 8, 2024
154 checks passed
@codeboten codeboten deleted the codeboten/update-scope-kubeletstatsreceiver branch August 8, 2024 18:57
@github-actions github-actions bot added this to the next release milestone Aug 8, 2024
f7o pushed a commit to f7o/opentelemetry-collector-contrib that referenced this pull request Sep 12, 2024
…en-telemetry#34537)

Update the scope name for telemetry produced by the
kubeletstatsreceiverreceiver from otelcol/kubeletstatsreceiver to
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kubeletstatsreceiverreceiver

Part of
open-telemetry/opentelemetry-collector#9494

---------

Signed-off-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants