Wrong choices happen when there's deletion of useful historical data, motivated by short-term cost saving.
Wrong choices also happen when there's unnecessary creation on data, such as logging and storing everything, just in case, with a verbose level.
Storage can be cheap in some cases, but high-availablility high-performance cloud storage is very expensive. Anyway, it's not infinite.
The way to keep useful data is to be strategic and only store relevant logs. Fine tune retention policy especially for fastest growing data. Storing everything on high-cost storage, without smart retention policy, could lead to deleting git data to make place for a mix of debug logs and random shit.
I thought it's about Retrospective meetings (dev process) , but it's about accumulated log data.
Wrong choices happen when there's deletion of useful historical data, motivated by short-term cost saving.
Wrong choices also happen when there's unnecessary creation on data, such as logging and storing everything, just in case, with a verbose level.
Storage can be cheap in some cases, but high-availablility high-performance cloud storage is very expensive. Anyway, it's not infinite.
The way to keep useful data is to be strategic and only store relevant logs. Fine tune retention policy especially for fastest growing data. Storing everything on high-cost storage, without smart retention policy, could lead to deleting git data to make place for a mix of debug logs and random shit.
I thought it's about Retrospective meetings (dev process) , but it's about accumulated log data.