Following a hack session with Openscapes (see https://github.com/2i2c-org/meta/issues/1578), Tasha (CryoCloud) expressed that she would like the option to extend the Prometheus data source collection beyond one year so that she can analyse YoY trends, e.g. quantify how many users are still active following a workshop. The AWS cost explorer is also limited to a 1-year range.
Collecting and storing this amount of data in Prometheus could be tricky -- is there a cost-effective alternative by exporting data on a yearly cadence?
Definition of Done
[ ] Check-in January 2025
[ ] Decide whether we have the capacity to investigate this
[ ] Conduct a small spike into investigation or put this issue into a backlog
Context
Following a hack session with Openscapes (see https://github.com/2i2c-org/meta/issues/1578), Tasha (CryoCloud) expressed that she would like the option to extend the Prometheus data source collection beyond one year so that she can analyse YoY trends, e.g. quantify how many users are still active following a workshop. The AWS cost explorer is also limited to a 1-year range.
Collecting and storing this amount of data in Prometheus could be tricky -- is there a cost-effective alternative by exporting data on a yearly cadence?
Definition of Done