Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't get GCP billing data from EU region #2755

Closed
SorsOps opened this issue May 19, 2024 · 2 comments
Closed

Can't get GCP billing data from EU region #2755

SorsOps opened this issue May 19, 2024 · 2 comments
Labels
E2 Estimated level of Effort (1 is easiest, 4 is hardest) kubecost Relevant to Kubecost's downstream project opencost OpenCost issues vs. external/downstream P1 Estimated Priority (P0 is highest, P4 is lowest)

Comments

@SorsOps
Copy link

SorsOps commented May 19, 2024

Describe the bug
Can't get GCP billing data for big query if not in location US

To Reproduce
Steps to reproduce the behavior:

  1. Create a GCP account and export the billing info from the EU region
  2. Attempt to read it

Expected behavior
That it either should read the data or give me the ability to configure the region

Screenshots

64266Z INF CloudCost[<REDACTED>/<REDACTED>.<REDACTED>]: ingestor: building window [2024-05-01T00:00:00+0000, 2024-05-08T00:00:00+0000)
2024-05-19T19:05:58.753164267Z ERR CloudCost[<REDACTED>/<REDACTED>.<REDACTED>]: ingestor: build failed for window [2024-05-12T00:00:00+0000, 2024-05-19T00:00:00+0000): error retrieving CUD rates: GetFlexibleCUDRates: queryCUDAmountPayed: query error BigQueryQuerier: Query: error reading query results: googleapi: Error 404: Not found: Dataset<REDACTED>:d<REDACTED> was not found in location US, notFound

Which version of OpenCost are you using?

  • ghcr.io/opencost/opencost-ui:1.110.0
@mattray
Copy link
Collaborator

mattray commented May 23, 2024

That looks like what I fixed in #2239

@mattray mattray added opencost OpenCost issues vs. external/downstream kubecost Relevant to Kubecost's downstream project P1 Estimated Priority (P0 is highest, P4 is lowest) E2 Estimated level of Effort (1 is easiest, 4 is hardest) and removed needs-triage needs-follow-up labels May 23, 2024
@mattray
Copy link
Collaborator

mattray commented Jun 5, 2024

This should be fixed in the next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E2 Estimated level of Effort (1 is easiest, 4 is hardest) kubecost Relevant to Kubecost's downstream project opencost OpenCost issues vs. external/downstream P1 Estimated Priority (P0 is highest, P4 is lowest)
Projects
None yet
Development

No branches or pull requests

2 participants