Make Tamland prediction length configurable by component
Problem Statement
Core service owners like the database and other foundational infrastructure usually require 3 milestones to perform the work, such as vertical scaling that is necessary to mitigate any saturation issues that could occur - Feedback item. There was also discussion around this in gitlab-org&8070 (comment 1255657944) .
With the current Tamland charts the prediction is about 3 months out into the future. This does not allow enough time to plan for required changes that need roughly 3 milestones of work.
Additionally, service owners would like to see a longer prediciton time, accepting a potential for lower accuracy to get a sense of whether the large investments that they make are affecting the trend and sending the team in the right direction long term.
Proposed Solution
We should make the Tamland prediction length configurable by service so that we are able to present different views/graphs with longer or shorter predictions depending on the needs of the service. It would be beneficial for vertically scaling services to have longer predictions.
MVC
- Adapt the current framework for prediction and chart generation to include a property to allow a longer prediction and a longer Date timeseries on the x axis
- Set the default behaviour to what it currently is doing now
- Increase the prediction for the Vertically scaling Database resources to 18 months
- Get Feedback from the Database team