After running in prod for a day I was able to do some napkin math and determine that 1000 checks would end up using 32GB of database storage for a year. While that sounds crazy, it helped give insights on future scaling and data retention limits.
This is VERY early speculation that I don't need to do, but I always enjoy doing for some reason.
The MVP focus has helped me ignore the future storage issue and consider the current data storage as doing something that doens't scale
I'd handle that issue by having a retention system that thins out the data based on age.
For example, the chance of a user needing to know what the response time was at 5.30am 4.5 months ago is very low - probably just storing a datapoint for the day would be fine.