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.

Sign up for GitHub

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

Jump to bottom

Dropped flows should identify CPU #94

Open
vakalapa opened this issue Mar 20, 2024 · 1 comment
Open

Dropped flows should identify CPU #94

vakalapa opened this issue Mar 20, 2024 · 1 comment
Labels
area/ebpf area/plugins type/enhancement New feature or request

Comments

@vakalapa
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Recently, we saw an issue where inside a particular node, packets were dropped on a particular CPU. However, kubectl top was not showing CPU running hot (because only few CPUs out of 32 were over burdened). Add the CPU number to the flow extension for drop.

cc: @anubhabMajumdar
@github-actions github-actions bot added the meta/waiting-for-author Blocked and waiting on the author label Mar 28, 2024
@vakalapa vakalapa removed the meta/waiting-for-author Blocked and waiting on the author label Mar 28, 2024
@hainenber hainenber mentioned this issue Apr 7, 2024
Closed
7 tasks
@hainenber
Copy link
Contributor

Hi there, I made a draft PR as an attempt to address this. Does this implement what you have in mind? 👀

@microsoft microsoft deleted a comment from github-actions bot Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ebpf area/plugins type/enhancement New feature or request
Projects
Retina Triage Board
Status: In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(plugin/packetparser): identify CPU as Flow metadata hainenber/retina
2 participants
@vakalapa @hainenber