CloudHealth Perspectives enable precision reporting. They let you create unique business groups that reflect different sets of analysis, management and evaluation criteria.

CloudHealth Perspectives Setup
Fig. 1  |  Group your assets into dynamic business groups called Perspectives. Set up perspectives by environment, function, finance costs, owner, and more.

CloudHealth collects and maintains a historical record of all the resources you use to operate your cloud. These can include both cloud-based (e.g. instances, volumes, VMs, Blobs, snapshots, etc.) and system-based (e.g. Chef nodes, cookbooks) resources. The platform proactively discovers assets, then lets you track them over their lifecycle. Perspectives are rule-based, allowing you to report from both an operational (e.g. applications, roles) and a business standpoint (e.g. departments, product lines).

With this flexibility, you can see your cloud ecosystem by workload, environment, customer, department, or COGS. Define unique Perspectives for corporate stakeholders in finance, engineering, and operations to align cloud infrastructure with business metrics.

Each Perspective contains Groups that reflect the way you want to assemble cloud assets and services. For example:

  • Finance needs a Service Perspective. The Service Groups include: Mobile App, Web Hosting, Help Desk
  • Engineering requests an Environment Perspective. The Environment Groups include: Development, Test, Staging, Production.

CloudHealth lets you easily define your Perspectives based on naming conventions unique to you (tags or metadata). Most importantly, you can eliminate tedious ongoing management with dynamic groups that automatically update as changes occur.

Perspectives are used throughout the CloudHealth platform to define data set analyses, cost allocation, reports, alerts, budgets, and reserved instance management. They can be combined to create specific data intersections like: Environment by Customer, or Product Line by Environment.