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

[proposal] add more metrics for koordlet for tracing each module/feature works well #1867

Closed
2 of 5 tasks
zwzhang0107 opened this issue Jan 24, 2024 · 3 comments
Closed
2 of 5 tasks
Labels
area/koordlet good first issue Good for newcomers help wanted Extra attention is needed kind/proposal Create a report to help us improve lifecycle/stale

Comments

@zwzhang0107
Copy link
Contributor

zwzhang0107 commented Jan 24, 2024

What is your proposal:

  • performance(qps/rt) from to kubelet
  • cri performace(qps/rt)
  • Runtime Hook Server performance
  • os file(cgroup) read and write duration
  • duration of system call

Why is this needed:

Is there a suggested solution, if so, please add it:

@zwzhang0107 zwzhang0107 added kind/proposal Create a report to help us improve good first issue Good for newcomers help wanted Extra attention is needed area/koordlet labels Jan 24, 2024
@saintube
Copy link
Member

link #987

Copy link

stale bot commented May 22, 2024

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close
    Thank you for your contributions.

Copy link

stale bot commented Jun 21, 2024

This issue has been automatically closed because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Reopen this PR with /reopen
    Thank you for your contributions.

@stale stale bot closed this as completed Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/koordlet good first issue Good for newcomers help wanted Extra attention is needed kind/proposal Create a report to help us improve lifecycle/stale
Projects
None yet
Development

No branches or pull requests

2 participants