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

Pod metrics are not collected in containerd runtime. #12638

Closed
vasireddy99 opened this issue Jul 21, 2022 · 4 comments
Closed

Pod metrics are not collected in containerd runtime. #12638

vasireddy99 opened this issue Jul 21, 2022 · 4 comments

Comments

@vasireddy99
Copy link
Contributor

vasireddy99 commented Jul 21, 2022

Describe the bug
When using Bottlerocket in EKS, otel-collector can not collect Pod metrics.
Log is bellow.

2022-03-20T14:04:42.986Z warn cadvisor/container_info_processor.go:93 No pod metric collected {"kind": "receiver", "name": "awscontainerinsightreceiver", "metrics count": 27}
Steps to reproduce

Create cluster with Bottlerocket
Set aws-otel-collector with aws-otel-collector/deployment-template/eks/otel-container-insights-infra.yaml
I use amazon/aws-otel-collector:v0.17.0 image.

This would required changes in awscontainerinsightsreceiver. Reference issue in distro

Steps to reproduce
If possible, provide a recipe for reproducing the error.

What version did you use?
Version: v0.54.0

What config did you use?

Additional context
Add any other context about the problem here.

@vasireddy99 vasireddy99 added the bug Something isn't working label Jul 21, 2022
@vasireddy99 vasireddy99 changed the title Pod metrics are not collected in containerd runtime. changes in awscontainerinsightsreceiver Pod metrics are not collected in containerd runtime. Jul 21, 2022
@github-actions
Copy link
Contributor

Pinging code owners: @Aneurysm9 @pxaws

@TylerHelmuth TylerHelmuth added the priority:p2 Medium label Jul 22, 2022
@vasireddy99
Copy link
Contributor Author

The fix to this issue has been fixed in this PR and is in out on #v0.57.2.

@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Nov 10, 2022
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants