[BUG] Jobs using `length`, `delay`, and `period` at the job level and metric level results in inconsistent start time and end time for GetMetricData queries about yet-another-cloudwatch-exporter HOT 1 OPEN

Just adding a note I realized,

3. Delay is only respected at the job level even though it's configurable at the metric level

Is especially bad because it will have very unintended consequences when fixed. Metric validation adds a default 5 minute delay to all metrics if they do not have a defined delay and the job does not have a defined delay. This default delay has largely been ignored because all example configs use no delay at the job level. As soon as this is fixed that delay will take effect potentially breaking the expected behavior for everyone. I'm still trying to think through how to approach this in a safe manner but felt it was necessary to write down.

from yet-another-cloudwatch-exporter.