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

Multi Cluster observability #2638

Open
OliverChmelicky opened this issue Mar 14, 2024 · 1 comment
Open

Multi Cluster observability #2638

OliverChmelicky opened this issue Mar 14, 2024 · 1 comment
Labels
doc needed Additional documentation is required E3 Estimated level of Effort (1 is easiest, 4 is hardest) needs-follow-up needs-triage opencost OpenCost issues vs. external/downstream P3 Priority (P0 is highest, P4 is lowest)

Comments

@OliverChmelicky
Copy link

Multi Cluster feature request
Would there be a way in the future how to monitor costs in multiple GCP GKE clusters?
Theoretically would it be possible to monitor multiple clusters from multiple Cloud Providers?

Final solution
See in one Opencost view costs pivoted per Cluster, per Project or per Cloud provider if possible.

Alternatives
An alternative would be to configure Prometheus to collect metrics from different clusters in the same project or multiple projects but still using one Cloud Provider. I am not sure whether there would be an option in Opencost UI to see costs aggregated per Cluster. But per Node they should be easy to separate even in the actual implementation.

@mattray
Copy link
Collaborator

mattray commented Mar 15, 2024

The most straightforward solution would be to use Prometheus forwarding sidecars to a centralized Prometheus-compatible database (Thanos, Mimir, etc.) and run Grafana against that. That's been independently implemented multiple times but it's not documented.

The OpenCost UI doesn't support that and you'd need some sort of API on top of that. But if all you want is basic observability, what I described above works.

@mattray mattray added opencost OpenCost issues vs. external/downstream doc needed Additional documentation is required E3 Estimated level of Effort (1 is easiest, 4 is hardest) P3 Priority (P0 is highest, P4 is lowest) labels Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc needed Additional documentation is required E3 Estimated level of Effort (1 is easiest, 4 is hardest) needs-follow-up needs-triage opencost OpenCost issues vs. external/downstream P3 Priority (P0 is highest, P4 is lowest)
Projects
None yet
Development

No branches or pull requests

2 participants