Skip to content

CLI command steps profiling and performance analytics #4243

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

Closed
6 tasks done
KristianDD opened this issue Dec 20, 2018 · 0 comments
Closed
6 tasks done

CLI command steps profiling and performance analytics #4243

KristianDD opened this issue Dec 20, 2018 · 0 comments
Assignees
Labels
Milestone

Comments

@KristianDD
Copy link
Contributor

KristianDD commented Dec 20, 2018

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

We have no means of analyzing the performance of CLI commands, when executed by our clients. This means that commands that run fast on our setup might be slow on a specific client setup and we will never know. Moreover we have no reference for average times of command execution and means of monitoring for performance degradation.

Describe the solution you'd like

Log analytic data about command execution time (and the steps included - prepare, build, etc.). There should also be a way of outputting this data in the console or into a file for problem investigation and monitoring.

Acceptance criteria

  • 1 Track data for command performance in analytics if usage-reporting is enabled
  • 2 --performance flag should output performance information in the output
  • 3 --performance pathToFile/someFile.txt should create the file and write performance information inside
  • 4 Each line in the performance output file should be a valid JSON
  • 5 Should have tracking information about: build, run, debug, create.
  • 6 Should include information about hooks execution time(for example before-prepare, after-prepare
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants