AjayTripathy
Joined 15 years ago
Karma
69
Submissions
32
Member since
Jul 15
Recent submissions
Comment · 3 years ago
Agree! That's the vision!
Comment · 5 years ago
No problem! Please let me know how we can help.
Comment · 5 years ago
Kubecost fully supports labels by default-- however until recent versions we relied on kube-state-metrics for that data, which requires users to whitelist the labels they want to see. If you upgrade to our latest version, I'd be surprised if this still wasn't working for you. Once you've upgraded, you can reach out to [email protected] if labels still aren't appearing or me personally [email protected] and I'd be happy to help troubleshoot.
Comment · 5 years ago
Each use case is different, but I think expiring the data after 60d in your monitoring stack makes sense both from a scaling perspective of your monitoring stack and from a privacy perspective.
I wouldn't necessarily put _user_ data in labels, but team/product names and contact info of the coworkers responsible for the service seem fine to me.
Comment · 6 years ago
Stackwatch | Backend Engineer | Full-time | Remote
Stackwatch is the company behind Kubecost https://github.com/kubecost/cost-model . We're building tools to help devops and finops work together to track, manage, and optimize containers in Kubernetes. We're a small team of 4 engineers and 1 salesperson today, all remote, and looking to grow. We're backed by some great investors and actively selling an open-code product to enterprise today.
You can email me directly at [email protected]
Comment · 6 years ago
There's definitely ways to do this by configuring your scrape configs to ignore sets of nodes. Curious though when you last tried kubecost out? We've built out some caching mechanisms in the product over the last month or so that should dramatically reduce load / memory consumption on prometheus. If you reach out on our slack kubecost.slack.com we can discuss more about expected Prometheus resource consumption.
Comment · 8 years ago
Hey, former Google Cloud SRE here-- now work on projects to help companies manage cloud spend. Prediction and especially recommendations for lowering cloud spend can get tricky, but I wrote a piece of software and some grafana dasboards that with one click can deploy and calculate cluster costs if you're using kubernetes. Obviously this doesn't include, say, s3 storage costs per bucket, and doesn't much help if you're not using kubernetes, but this is just a first step.
More general solutions can be instrumented with cloudhealth https://www.cloudhealthtech.com/, but that's a bit more of an enterprise-y solution.
https://medium.com/kubecost/effectively-managing-kubernetes-...
Comment · 8 years ago
Helm chart author here-- let me know if you have any feedback! I wanted to build a one or two click way to quickly get cost metrics on GKE.