
What I like most about Tanzu CloudHealth is that it serves as a single source of truth for multi-cloud FinOps governance. When you’re juggling different billing logic and native cost tools across AWS, Azure, and Google Cloud, it becomes extremely difficult to keep a consistent, standardized budgeting baseline. CloudHealth addresses this by bringing all of that disparate billing metadata together into unified dashboard views.
The feature I depend on most is Perspectives. It allows us to dynamically allocate cloud infrastructure spend directly to specific engineering teams, projects, or cost centers. As a result, it removes much of the usual guesswork from internal chargeback reporting and helps create real financial accountability across the organization. Review collected by and hosted on G2.com.
What frustrates me most about Tanzu CloudHealth is the noticeable lag in data synchronization. When you’re managing massive multi-cloud environments, real-time cost visibility is critical, yet billing metrics often suffer from sync delays. That latency makes it very hard to spot live cost spikes before they blow past a daily threshold.
On top of that, the web client interface has grown increasingly complex and harder to navigate over time. Finding advanced reporting configurations, or even adjusting simple notification profiles, can mean hunting through deeply buried sub-menus, which really hurts efficiency during routine auditing tasks. Review collected by and hosted on G2.com.


