-
Notifications
You must be signed in to change notification settings - Fork 74
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
Combine metric profiles #438
Conversation
Signed-off-by: Raul Sevilla <[email protected]>
Signed-off-by: Raul Sevilla <[email protected]>
Signed-off-by: Raul Sevilla <[email protected]>
/rerun all |
Results for e2e-benchmarking CI Tests
|
/rerun all WORKLOAD=node-density ./run.sh |
Results for e2e-benchmarking CI Tests
|
/rerun all kube-burner:WORKLOAD=node-density ./run.sh |
Results for e2e-benchmarking CI Tests
|
@rsevilla87 thoughts on reviewing and updating this PR's logic #411 here? or closing it if it's no longer relevant? |
/rerun all kube-burner:WORKLOAD=node-density ./run.sh |
Results for e2e-benchmarking CI Tests
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Let's put this one on hold, I have to make some change in the grafana report to ensure we don't loss any interesting metric |
Description
Combine metrics-aggregated.yaml and metrics.yaml files.
I managed to combine them thanks to expressions such as:
Which uses the magic variable {{ .elapsed }} which takes the value of the benchmark duration. Now, in large-scale deployments we won't collect metrics for all worker nodes (which is overkill) but instead we'll collect metrics for the 3 worker nodes with more kubelet CPU usage, same for other similar metrics.