You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
usage-reporting
is enabled--performance
flag should output performance information in the output--performance pathToFile/someFile.txt
should create the file and write performance information insideJSON
before-prepare
,after-prepare
The text was updated successfully, but these errors were encountered: