While "yesterday" is technically the most correct way to query
exactly 1 day of data right now, it shows unexpected empty
responses for users who have just installed Kubecost and have
no data for yesterday. This introduces a better default experience
for new users.
I chose 1d instead of today because today can seriously underreport if the time is just after UTC midnight. 1d will likely slightly overreport but that overreporting is temporary and will be automatically resolved by the release and deployment of hourly ETL.
While "yesterday" is technically the most correct way to query exactly 1 day of data right now, it shows unexpected empty responses for users who have just installed Kubecost and have no data for yesterday. This introduces a better default experience for new users.
I chose
1dinstead oftodaybecausetodaycan seriously underreport if the time is just after UTC midnight.1dwill likely slightly overreport but that overreporting is temporary and will be automatically resolved by the release and deployment of hourly ETL.