fermyon / spinkube-performance

A SpinKube Performance Test Suite
Apache License 2.0
1 stars 3 forks source link

Add new `template_variable_presets` to dashboard after successful run #44

Open kate-goldenring opened 4 months ago

kate-goldenring commented 4 months ago

Ideally we could push a new preset to the dashboard after each successful run

API usage would be similar to the following: https://gist.github.com/lrascao/f57312ff33b799c4c0db56b10e80fe26

We'd update the `` section to add another entry. For example, this:

"template_variable_presets":[{"name":"03-03-1714779130026-1714780634987","template_variables":[{"name":"node_os","value":"linux"},{"name":"node_arch","value":"amd64"},{"name":"node_instance_type","value":"standard_a2_v2"},{"name":"host","value":"aks-apps-83635121-vmss000000-aks-ci-spinkube-perffa0341ed"},{"name":"test_id","value":"8946034691"}]}]

Is expanded to have a second entry:

"template_variable_presets":[{"name":"03-03-1714779130026-1714780634987","template_variables":[{"name":"node_os","value":"linux"},{"name":"node_arch","value":"amd64"},{"name":"node_instance_type","value":"standard_a2_v2"},{"name":"host","value":"aks-apps-83635121-vmss000000-aks-ci-spinkube-perffa0341ed"},{"name":"test_id","value":"8946034691"}]},{"name":"05-04-1714789130500-1714790634900,"template_variables":[{"name":"node_os","value":"linux"},{"name":"node_arch","value":"amd64"},{"name":"node_instance_type","value":"standard_a2_v2"},{"name":"host","value":"aks-apps-1234567-vmss000000-aks-ci-spinkube-perffxxxx"},{"name":"test_id","value":"99999999"}]}]
vdice commented 4 months ago

By preset do you mean a new entry in this dropdown?

Screenshot 2024-05-10 at 10 31 30 AM
kate-goldenring commented 4 months ago

Yes exactly. It may make sense to include the timestamp (TS) in the name to (as in 03-03-TS_START-TS_END one) so they can filter to the appropriate time too