Chart controls and notes
Showing the first 20 categories. Open full screen to explore all 37 categories.
FinOps Practitioners must identify if there are any data residency/ localization/ sovereignty inconsistencies. In order to identify any potential anomalies, they would like to see if the resource being billed for exists in the same geography as the primary payer account. If they do not exist in the same geography, the team would like it flagged for analysis.
This query uses the Provider column. Provider is deprecated in v1.3 and will be removed in v1.4.
Column names from the source use case.
Showing the first 20 categories. Open full screen to explore all 37 categories.
Showing 100 of 500 rows. Scroll inside the table to see more.
select provider_name,
sub_account_id,
region_id,
region_name,
count(*) as charge_count
from focus.cost_and_usage
where charge_period_start >= $1::timestamptz
and charge_period_end < $2::timestamptz
group by 1, 2, 3, 4
order by charge_count desc, provider_name, sub_account_id, region_id
limit 500SELECT ProviderName, SubAccountId, RegionId RegionName, COUNT(1) FROM focus_data_table WHERE ChargePeriodStart >= ? AND ChargePeriodEnd < ? GROUP BY ProviderName, SubAccountId, RegionId, RegionName