Treat deploy as an action that takes time, instead of instantaneous
It would be awesome, since we know a lot of about the deploy job due to integration with GitLab CI, to provide more detail on the deploy job in the monitoring workflows. Currently we seem to count a deploy as when the job started, and put a bar on the chart, which is great. But as we all know, deploys can take time (minutes, hours?) so this can be greatly inaccurate. Deploys can also fail. We should enhance our knowledge and presentation of deploys to take into account these conditions: **Performance dashboard:** 1. Instead of a single bar to denote a deploy, we should show a shaded column representing the start and end of the job. 1. The shading could be a light green to indicate a successful deploy, or a red to indicate a failed deploy. This way it is extremely clear if strange things are happening with the metrics, that a failed deploy could be the culprit. 1. I think the flag can largely be as is, and we simply update add the deploy data when you are hovering over a the deploy column. **MR widget** 1. Similar to the dashboard, we should show a column on the sparkline to indicate the deploy window. 1. The calculation of the before/after metrics should begin on the boundaries of the deploy window. For example if a deploy took 10 minutes, we should calculate 30 minutes before and 30 minutes after the end.
issue