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

Track performance of odo logs command #6014

Closed
3 tasks
rm3l opened this issue Aug 8, 2022 · 2 comments
Closed
3 tasks

Track performance of odo logs command #6014

rm3l opened this issue Aug 8, 2022 · 2 comments
Labels
area/log Issues or PRs related to `odo logs` area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/user-story An issue of user-story kind lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@rm3l
Copy link
Member

rm3l commented Aug 8, 2022

/kind user-story

User Story

  • As an odo developer
  • Now that odo logs has been improved when used against remote clusters (odo logs too slow for non-local clusters #5872), I want to track and monitor its performance
  • So that we can catch potential regressions in the future before they hit users

Acceptance Criteria

  • It should track performance on a continuous or nightly basis
  • It should record performance data somewhere, so we can easily view and perform statistical analysis
  • Implementation should be open for extensibility, as we might need to track performance data for other commands

Notes

Links

/kind user-story

@openshift-ci openshift-ci bot added the kind/user-story An issue of user-story kind label Aug 8, 2022
@rm3l rm3l added the area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering label Aug 8, 2022
@rm3l rm3l added this to odo Project Oct 3, 2022
@rm3l rm3l moved this to To Do 📝 in odo Project Oct 3, 2022
@rm3l rm3l removed the status in odo Project Oct 3, 2022
@rm3l rm3l added the priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. label Feb 9, 2023
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 29, 2023
@rm3l rm3l added the area/log Issues or PRs related to `odo logs` label Sep 29, 2023
@github-actions
Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 30, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Oct 30, 2023
@rm3l rm3l closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/log Issues or PRs related to `odo logs` area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/user-story An issue of user-story kind lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
Archived in project
Development

No branches or pull requests

1 participant