search

iter8-tools / iter8

Kubernetes release optimizer
https://iter8.tools
Apache License 2.0
254 stars 34 forks source link

`github` and `slack` tasks #1568

Closed Alan-Cha closed 1 year ago

Alan-Cha commented 1 year ago

The github and slack tasks sent the experiment result to GitHub and Slack respectively. This included the status of the experiment, metric data, SLOs and whether they have been validated or not, etc., but with the upcoming changes for v0.16, all of these will be removed from the experiment result except for the experiment status.

Is it still worthwhile to keep the github and slack tasks? Some current options are just to send the experiment result as is, which only contains information about how tasks have been run and whether the experiment has completed or not, or to send the raw Fortio and ghz results from the http and grpc tasks.

Related to #1566

Alan-Cha commented 1 year ago

We can keep the summary, which is essentially the following:

  Experiment completed: true
  No task failures: true
  Total number of tasks: 4
  Number of completed tasks: 4

and we can also add the name and namespace of the experiment.