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 stats get duplicated in some situations #278

Closed
puckpuck opened this issue Aug 16, 2022 · 2 comments
Closed

pod stats get duplicated in some situations #278

puckpuck opened this issue Aug 16, 2022 · 2 comments

Comments

@puckpuck
Copy link
Contributor

The agent seems to return 2 events for the same pod on some collection cycles (not all). With closer examination only the metrics.uptime, and sometimes the network metrics are different but all other stats are the same. There should only be a single event per pod per collection cycle returned.

This may be due to the kubelet returning the same pod multiple times when pulled for stats.
This query on the Honeycomb demo team shows the issue: https://ui.honeycomb.io/demo/environments/ms-demo/datasets/kubernetes-metrics/result/ywxDQmCmhMP
https://houndsh.slack.com/archives/CDE86Q55X/p1660658679350499

@vreynolds vreynolds added the status: oncall Flagged for awareness from Honeycomb Telemetry Oncall label Aug 17, 2022
@MikeGoldsmith MikeGoldsmith self-assigned this Aug 24, 2022
@kentquirk
Copy link
Contributor

@puckpuck This turned out to be ... complicated. We're currently putting it in the icebox pending capacity to deal with it properly.

@JamieDanielson JamieDanielson removed the status: oncall Flagged for awareness from Honeycomb Telemetry Oncall label Nov 28, 2022
@MikeGoldsmith MikeGoldsmith removed their assignment Feb 6, 2024
@MikeGoldsmith
Copy link
Contributor

We are trimming our OSS backlog. We will be closing this issue as it is a low priority for us to fix. It is unlikely that we'll ever get to it, and so we'd like to set expectations accordingly.

If this issue is important to you, please feel free to ping here and we can discuss/re-open.

@MikeGoldsmith MikeGoldsmith closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants