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
make perfomrance pr-bot to use json output #9939
Comments
@priyawadhwa can you please explain about this issue |
Hey @Aut0R3V -- we have a binary called
mkcmp is responsible for comparing start time between two minikube binaries. It runs each binary three times and outputs information around how long it took. This output is pasted on our PRs by our PR bot (example) You can build the binary locally by running:
Right now, we split up how long Instead of timing by logs to STDOUT, it would be better if we used the JSON output feature in minikube to more accurately parse logs and match up how long different steps take. This would require running |
Thanks a lot for the detailed explanation! |
/assign |
@Aut0R3V thanks for taking this issue on! |
@priyawadhwa I had some questions : 1] What changes are to be added at the already existing mkcmp workflow ? 2] Is this the correct defaultTimeFormat for the output : kubelet: {{.Kubelet}} apiserver: {{.APIServer}} kubeconfig: {{.Kubeconfig}} |
Hey @Aut0R3V --
Basically, instead of streaming logs from STDOUT and timing how long each of them takes, we want to swtich to streaming JSON logs. JSON log steps have the following format: {"data":{"currentstep":"0","message":"minikube v1.12.1 on Darwin 10.14.6\n","name":"Initial Minikube Setup","totalsteps":"10"},"datacontenttype":"application/json","id":"68ff70ae-202b-4b13-8351-e9f060e8c56e","source":"https://minikube.sigs.k8s.io/","specversion":"1.0","type":"io.k8s.sigs.minikube.step"} We want to parse out the "name" of the step from the JSON output and use that, instead of the full text output. That would mean replacing this line: minikube/pkg/minikube/perf/logs.go Line 54 in fdab252
with
This issue is definitely complicated, so thanks for your interest! |
Thanks for your help! |
@priyawadhwa is there any specific file where the logs would be coming to? |
Hey @Aut0R3V we get the logs by reading STDOUT from this command as it is running: minikube/pkg/minikube/perf/logs.go Line 45 in fdab252
|
@Aut0R3V, we haven't heard back from you for some time, are you still working on this issue? |
not needed anmore |
for more information ask @priyawadhwa
The text was updated successfully, but these errors were encountered: