a minimum and a target for outputs

[achimgaedke]

Maybe it would be great to have 2 fields to compare telemetry values from the outputs:

• a bare minimum, if that is not reached, the service is "malfunctioning"
• and a target, which can be achieved or missed (e.g. 90% 'under-performing') or over-fulfilled (great, one can save money here!).

Furthermore:

I've stumbled upon the field Output.delivery_date and nobody knows why it is there:

The field minimum was called target once upon a time, and it was implemented alongside with delivery_date. And then the name was changed to minimum. I'll put an "enhancement" ticket in, so we can discuss, whether the minimum and the target are useful together. The functionality of delivery_date might be achieved with an event modifying the minimum.

[Or4c]

I like this suggestion. Seems to cover all the bases. We should definitely nix the delivery_date as it seems to be a 'phantom limb'