Disable BigQuery recommendations that are not accurate.
We had identified a bug in the BigQuery FinOps dashboard that affected few metrics:
Potential Savings
Partition Your tables
BigQuery Explorer (Project, Dataset, Table)
As customers are using the dashboard and we don't have an ETA yet for ...
Recommendations overlap each other, so the final “potential savings” is not accurate because it is not achievable.
for example, On our demo project, we are showing savings of 88%! ( 3170 / 3643)
is it possible that current logic will show custom...
The recommendation Suggests reducing repeating queries by 10-50%.
I think that showing "change Repeating queries frequency" by percentage is not actionable and does not fit the real-world use cases.
Why are there repeated queries?
Business data ...
[Bug] Changing the reduce by % change the queries order
The order of the queries might get changed due to calculating on the raw data but showing only rounding results.
the change in savings should be linear and hence should not change the order.
while the data is getting updated on the dashboard, the percentage is jumping up and down.
The scan is completed, and 81% of your data was already processed. You are almost there!
>>
The scan is completed, and 38% of your data was already p...
Some recommendations in bigquery finops might not be relevant due to business logic needs.
For example:
the recommendation to "Enforce partition fields" when a full table scan is needed.
the recommendation to "reduce repeated query" when there i...
Users storing and moving large amounts of data in GCS could very much benefit from reports that show recommendations like “lower storage class for this rarely accessed bucket”, a scenario planner for cost during a disaster recovery from cold-line ...
