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
Currently the upgrade test only captures the pass/fail status based on the cluster being able to upgrade or not. We need to capture metrics including the ones we monitor manually to determine the cluster stability and index them long term similar to cluster density runs to be able to analyze the state of the cluster during/after the upgrade. This is especially useful in CI runs.
Kube-burner binary can be leveraged to just call the indexing given a metrics profile to capture and index them in ES and eventually visualized in Grafana. We can use the same metrics aggregated profile that cluster density test uses to start with.
The text was updated successfully, but these errors were encountered:
Currently the upgrade test only captures the pass/fail status based on the cluster being able to upgrade or not. We need to capture metrics including the ones we monitor manually to determine the cluster stability and index them long term similar to cluster density runs to be able to analyze the state of the cluster during/after the upgrade. This is especially useful in CI runs.
Kube-burner binary can be leveraged to just call the indexing given a metrics profile to capture and index them in ES and eventually visualized in Grafana. We can use the same metrics aggregated profile that cluster density test uses to start with.
The text was updated successfully, but these errors were encountered: