IBM Kubecost vs. MEDsys

We found that IBM Kubecost was a great fit for multi-tenant clusters that had shared resources. It broke the clusters down in namespaces, deployment labels, pods, etc. Dynamic monitoring is another asset - any accidental configuration that is not optimal and is causing spike in the consumption can be caught in a few hours

Incentivized

• Show namespace level cost and usage
• Allow rightisizibg At namespace level
• Show effectiveness of current resources allocation

Incentivized

• I think there is room for improvement in IBM Kubecost if you Streamline IBM Kubecost more with AWS cost explorer

Incentivized

While Kubecost is very critical tool, providing useful information about your organization's kubernets cost patterns, it could use additional features like better integration with other IBM tools. Having the ability to incorporate other IBM tools will be helpful for users and leadership as well as increase overall awareness of what other Products IBM provides.

Incentivized

Very comparable tools but given that we are not a SaaS company, we didn't opt for CloudZero which could have been a better fit if we were a SaaS company and needed granular unit cost tracking and cross platform visibility. Datadog was also considered but it required a lot of upfront investment to get up and running

Incentivized

• Allowed individual teams to better their cloud architecture for cost efficiency
• Save on cloud investment

Incentivized