Chart controls and notes
Showing the first 20 categories. Open full screen to explore all 50 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.
Column names from the source use case.
Showing the first 20 categories. Open full screen to explore all 50 categories.
Showing 100 of 500 rows. Scroll inside the table to see more.
select case when publisher_name is not null and publisher_name is distinct from invoice_issuer_name then publisher_name else provider_name end as service_provider_name,
sub_account_id as sub_account_id,
region_id as region_id,
region_name as region_name,
count(1) as row_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 row_count desc, service_provider_name, sub_account_id nulls last, region_id nulls last, region_name nulls last
limit 500SELECT ServiceProviderName, SubAccountId, RegionId, RegionName, COUNT(1) FROM focus_data_table WHERE ChargePeriodStart >= ? AND ChargePeriodEnd < ? GROUP BY ServiceProviderName, SubAccountId, RegionId, RegionName