Add `usage_start_time` and `usage_end_time` to GCP billing SQL queries
Open
bug
Team:Obs-InfraObs
- Dominant language
- Go
- Stars
- 12.7k
- Forks
- 5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 364
Description
Billing export data ingested shows incorrect daily costs because the Lens visualization relies on `@timestamp`, which reflects ingestion time rather than when the cost was incurred. As a result, historical costs appear on the ingestion date instead of their actual usage period.
We need to update the SQL queries to include `usage_start_time` / `usage_end_time` and adjust the visualization to use those fields as the time axis.
Contributor guide
Assessment
This issue has not been assessed yet.