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

Failed OpenCost integration to GCP #2742

Open
stefano-arre opened this issue May 9, 2024 · 7 comments
Open

Failed OpenCost integration to GCP #2742

stefano-arre opened this issue May 9, 2024 · 7 comments
Assignees
Labels
E2 Estimated level of Effort (1 is easiest, 4 is hardest) needs-follow-up opencost OpenCost issues vs. external/downstream P1 Estimated Priority (P0 is highest, P4 is lowest)

Comments

@stefano-arre
Copy link

Describe the bug

Following step by step the installation guide, Opencost 1.110 fails the integration to GCP.

Screenshot 2024-05-09 alle 17 04 20

These are the logs:
Screenshot 2024-05-09 alle 17 05 09
Screenshot 2024-05-09 alle 17 05 40

In this ticket the topic was already mentioned.

To Reproduce
I just follow the installation guide.

Which version of OpenCost are you using?
1.110

@mattray
Copy link
Collaborator

mattray commented May 10, 2024

@stefano-arre did it clear up like in the linked ticket, or still broken?

@mattray mattray added opencost OpenCost issues vs. external/downstream P2 Estimated Priority (P0 is highest, P4 is lowest) E2 Estimated level of Effort (1 is easiest, 4 is hardest) labels May 10, 2024
@stefano-arre
Copy link
Author

Unfortunately, it is still broken.

I had a doubt here:
image

I can not see the <BILLING_DATA_DATASET> attribute in the cloud-integration.json example, and I guessed I had to split the prefix "billing.data" and the name of the table "gcp_billing_export_v1..."

This is the first part of my cloud-integration.json file:
image

Is it correct? Where should I add the <BILLING_DATA_DATASET>?

@dholeshu
Copy link

+1
Im seeing the same issue in 2 different gcp clusters running opencost v1.110

@iamdmitrij
Copy link

I'm using Grafana K8S monitoring with OpenCost enabled on AKS Kubernetes on Azure: https://github.com/grafana/k8s-monitoring-helm and logs show exactly same issue. I'm not using OpenCost UI, but Grafana Cloud does display pricing properly with this error present in the pods.

Version: ghcr.io/opencost/opencost:1.110.0 running on Azure.

@mattray
Copy link
Collaborator

mattray commented May 14, 2024

I'm getting the same issue with a previously working API key. I generated a new one slotted for Cloud Billing API and it still fails. I'll raise it with Kubecost Engineering.

@mattray mattray added P1 Estimated Priority (P0 is highest, P4 is lowest) and removed P2 Estimated Priority (P0 is highest, P4 is lowest) labels May 14, 2024
@mattray
Copy link
Collaborator

mattray commented May 14, 2024

Confirmed with my personal account with a fully privileged API key.

@cliffcolvin
Copy link
Member

Created a ticket for this and will get assigned this week.

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) needs-follow-up opencost OpenCost issues vs. external/downstream P1 Estimated Priority (P0 is highest, P4 is lowest)
Projects
None yet
Development

No branches or pull requests

5 participants