Use lag trend ratio instead of percent

See merge request !184

Update grafana dashboard to show topics of ospbench

See merge request !182

Add terminationGracePeriodSeconds of 0 to end pods in executions directly

See merge request !183

Fix bug while deleting a running exection

See merge request !181

make excpetion handling understandable

Closes #247

See merge request !179

Add a Patcher to handle ospbench data volume settings

See merge request !174

Björn Vonheiden authored 3 years ago and Sören Henning committed 3 years ago

This handler takes the total defined load and compute the
needed load generator instances and set the volume that each generator
should generate

Fix "Deployment not deleted with Flink"

Closes #248

See merge request !177

Use the properties of the slo checker and add lag trend percent

Closes #243

See merge request !172

The percentage lag trend is at the moment only available for the NumSensors
load type, because for NumNestedGroups it makes no sense.

Specific slo checker should be defined with a propertie map to be more generic.
Further add a lag trend percent slo, which use a percentage of the defined load
to compute the allowed threshold.

Enhance Code Quality

Closes #209

See merge request !168