Integrating with VMware Services

Integrate with VMware Aria Operations for Applications

Allow VMware Tanzu CloudHealth to ingest the usage and performance data that Operations for Applications gathers.

Why Use Operations for Applications

Operations for Applications is a SaaS service that records and manages time-series metrics for your cloud assets and resources. You can use these metrics to gain insights into usage, performance, and other analytics. Operations for Applications gathers the time-series data through integrations that are specific to the cloud asset. For example, Operations for Applications has integrations for Amazon EC2, Azure Virtual Machine, Google BigQuery, and so on. For more information, see Operations for Applications Documentation.

Benefits of Operations for Applications Integration

Tanzu CloudHealth ingests the usage and performance data that Operations for Applications gathers to help you in the following ways:

  • Understand how your cloud assets are being allocated and utilized through usage reports
  • Make rightsizing decisions for EC2 Instances and Azure Virtual Machines
  • Use Operations for Applications Source attributes such as tags or fields to categorize assets into Perspectives

Connect Operations for Applications Account

  1. In the Tanzu CloudHealth platform, from the left menu, select Accounts > Setup > VMware Aria Operations for Applications.
  2. Click Add Account.
  3. Name the account.
  4. Retrieve the API token for your Operations for Applications account and paste it in the API Key field. An Operations for Applications API token is tied to the Operations for Applications user account. Ensure that the user account whose API token you select has access to the Operations for Applications Sources that you want to ingest in the Tanzu CloudHealth. For information on retrieving your Operations for Applications API token, see Invoking the API.
  5. Only if you are using a metric prefix in Operations for Applications, enter its value in the Metric Prefix field.
  6. If you would like to import tags from a legacy Servers account, enable Import tags. Tanzu CloudHealth then actively collects tags, and you will see an additional field to accept the tags that you want to import into Tanzu CloudHealth.

  7. Click Save Account.

    Tanzu CloudHealth begins collecting Operations for Applications Sources within 15 min of account setup. Thereafter, Operations for Applications Sources are collected every 15 min. Tanzu CloudHealth fetches up to one day’s worth of time-series data from the date when you add the Operations for Applications account.

Operations for Applications Data Collection

What Operations for Applications data does the Tanzu CloudHealth Platform Gather

  • Operations for Applications Sources every 15 minutes. Sources can have tags attached to them.
  • Operations for Applications Source tags every 15 minutes. Operations for Applications Source tags are treated as dynamic attributes on an Operations for Applications Source. You can use Operations for Applications tags to build Perspectives. You cannot overwrite Operations for Applications Source tags with custom Tanzu CloudHealth tags.
  • Memory and disk metrics every 1 hour. For each metric, the mean, minimum, and maximum values are gathered.
  • If you have enabled CloudWatch metrics collection through the Tanzu CloudHealth platform, core metrics such as CPU, network bytes, and filesystem usage are gathered.

Operations for Applications Within the Tanzu CloudHealth Platform

Perspectives

You can use VMware Aria Operations for Applications source tags to create Perspective Groups within the Tanzu CloudHealth platform.

  1. In the Tanzu CloudHealth platform, navigate to the Perspective editor.
  2. From the Choose an Asset Type dropdown, select VMware Aria Operations for Applications > Source. Set the Discovery Method to Categorize.
  3. From the Choose a Field to Categorize By dropdown, select the tag that you want to use for creating Perspective groups.

Rightsizing

Tanzu CloudHealth ingests Operations for Applications metrics - Memory, CPU, network bytes, and filesystem usage for EC2 Instances and displays these metrics in the Rightsizing Report.

Integrate with Tanzu CloudHealth Agent

Integrate with the Tanzu CloudHealth Agent to allow the Agent to take snapshots at specific intervals and report metrics to the Tanzu CloudHealth platform every hour.

What Is the Tanzu CloudHealth Agent

The Tanzu CloudHealth Agent is a lightweight monitoring service for your cloud resources. It is based on the collectd daemon. You can install the Agent on your cloud instances to gain system-wide visibility into CPU, file system, and memory utilization. If you have Docker, the Agent catalogs containers and images as well.

Once installed, the Agent takes snapshots at specific intervals and reports metrics to the Tanzu CloudHealth platform every hour. The Agent pushes data from the instance to the Tanzu CloudHealth endpoint over https. The data is in the form of a JSON file containing the aggregated disk I/O, filesystem, and memory metrics.

To understand the Agent transmission rates, see the Tanzu CloudHealth Knowledge Base article.

Note

  • The Tanzu CloudHealth Agent is unrelated to the Kubernetes agent.
  • Currently, Tanzu CloudHealth does not support ARM 64 processor.

Operating System Support

The Agent supports these server operating systems.

  • Ubuntu 12.04 and above
  • RHEL 6.5 and above
  • Amazon Linux 2014.09 via RPM or DEB packages
  • Windows Server 2008 R2 and above.

Tanzu CloudHealth Agent Version History

For Linux

Tanzu CloudHealth Agent Version Release Date Features Introduced Supported Instances
v28 09/03/2023 ARM Support, IMDsv2, TLS1.2 ARM DEB/RPM (Centos >=8/ x86_64), AMD DEB/RPM (Centos >=x86_64), RHEL >=8.0, UBUNTU >=20.0.0, Ubuntu 20 20.04.3 LTS (Focal Fossa). No more support to UBUNTU <12.04 and RHEL < 6.5.
v24 20/04/2021 Restricted to TLSv1.2. Hardstop for TLS 1.0, 1.1 Amazon Linux 2 AMD, UBUNTU < 20.0.0, CentOS > =7 (rhel fedora), RHEL >= 8.2
v23 21/01/2021 Resolved security violations Deprecated, No more support
v20 24/09/2018 Disabled auto-update at the agent level Deprecated, No more support
v19 13/02/2018 Support for proxies, default configuration parameters, instance ID collection fallback Deprecated, No more support
v18 03/03/2017 Standard version Deprecated, No more support

For Windows

Presently we have Tanzu CloudHealth Agent v22 with TLSv1.2 enabled.

NOTE: The auto-update feature has been disabled.

Install and Configure Tanzu CloudHealth Agent

If you have an older version of the Agent installed, uninstall it first by following the instructions in Troubleshoot Errors section.

  1. In the Tanzu CloudHealth platform, from the menu, select Setup > Data Collection > Agents and click Agent Settings.
  2. On the Configuration page, expand How to Install.

  3. Under Linux / Windows> No proxy setup > To install, enter the following command:

    wget https://s3.amazonaws.com/remote- collector/agent/v24/install_cht_perfmon.sh -O install_cht_perfmon.sh; sudo sh install_cht_perfmon.sh 24 api-key cloud-name

  4. Configure Agent settings to specify which metrics to collect and what sampling intervals to use.
    • Based on the OS of your server and, optionally, your proxy setup requirements, follow the instructions for installing the Tanzu CloudHealth Agent.
    • The Windows-specific command installs the Agent and creates a log file in the current directory that details the install process for troubleshooting.
    • Files are installed in this location: C:\Program Files (x86)\CloudHealth Technologies\
    • In addition, several registry keys are set at this location: HKEY\_LOCAL\_MACHINE\Software\CloudHealth Technologies
  5. Click Save Agent Settings.

Tanzu CloudHealth Agent with TLSv1.2

Tanzu CloudHealth Platform no longer supports the use of TLSv1.0 and TLS1.1 for API utilized by Tanzu CloudHealth Agent. You will see no impact due to the deprecation if you are not using Tanzu CloudHealth Agent. However, if you are using the Agent, TLSv1.2 will be supported. Modern servers will have no impact as this version of TLS was released in 2008.

The Tanzu CloudHealth Agent for Linux and Windows collects CPU, Memory, and Filesystem metric data from the instance operating system. This data is used in Policies, Rightsizing, Reporting for understanding and optimizing instance use. Metric data is collected at specific intervals and sent to the platform. Most instances use the latest version of TLSv1.2.

Upgrade your Tanzu CloudHealth Agent to v24 with TLSv1.2. Installing the latest version of Agent will automatically upgrade it to v24. On noticing errors, follow the steps under the Troubleshoot Errors section for manually fixing these errors.

Leverage Metrics from the Agent

AWS EC2 Instance Rightsizing

While CloudWatch metrics provide detailed performance information from outside the VM, the Agent provides information from the point of view of the operating system. This information allows Tanzu CloudHealth to calculate a score reflecting how well provisioned resources are utilized.

For more information, see Rightsizing by Instance.

AWS EBS Volume Rightsizing

Agent data provides visibility into file system utilization, which Tanzu CloudHealth uses to determine the usage of provisioned storage capacity.

For more information, see Rightsizing by Volume.

Troubleshoot Errors

Uninstall and Reinstall the Agent

On seeing errors, you can try manually uninstalling the Agent and then reinstall by following the commands below:

  1. Uninstall the Agent.
    wget -O - https://s3.amazonaws.com/remote- collector/agent/v24/uninstall_cht_perfmon.sh sudo sh; sudo rm -rf cht_agent_install/; sudo rm -rf install_cht_perfmon.sh

  2. Reinstall the Agent.
    wget https://s3.amazonaws.com/remote- collector/agent/v24/install_cht_perfmon.sh -O install_cht_perfmon.sh; sudo sh install_cht_perfmon.sh 24 <api_key> <cloud_name>;

Contact Tanzu CloudHealth Support Team

For further errors, reach out to the Tanzu CloudHealth support team (mail to: [email protected]) with the following information:

  • System Details

     $ uname       #current operating system
 $ uname -a    #including the operating system name, version, and build number, as well as the hardware architecture and release  level of kerel
 $ hostname    #hostname details
 $ lscpu       #provides a detailed overview of the system's CPU architecture, including the number of CPUs, cores, and threads, the clock speed, the cache size, and the address size
 $ cat os-release  #get os-details

  • Log in to the agent instance and get the installation logs

    $ cat /tmp/agent_install_log.txt

  • Check the status of cht collectd daemon

    $  ps -eaf | grep cht

  • Check the permissions on the collectd configuration file

    $ ls -alh /etc/chtcollectd/collectd.conf

  • Check collectd config

    $  vi /etc/chtcollectd/chtcollectd.conf
or $ vi /etc/chtcollectd/collectd.conf

  • Check the permissions of collecd and gather the content of the collector output directory and its subdirectories [metrics are collected if folders are present]

    $ ls -alR /var/lib/chtcollectd
$ vi /var/lib/chtcollectd/last_docker_upload.txt #check inside on file stamp details.

  • Once metrics are available, check if it is reaching to Tanzu CloudHealth endpoint Tanzu CloudHealth Agent collects metrics from the instance and sends them to the platform at endpoint api.cloudhealthtech.com at port 443.

    $ curl https://api.cloudhealthtech.com/v1/health  #should give happy
$ nslookup api.cloudhealthtech.com  or dig api.cloudhealthtech.com # should give 6,7 ips

  • Check the collectd and perfmon services status and start/restart accordingly

    $ sudo /etc/init.d/chtcollectd status/start/stop/restart
$ sudo /etc/init.d/cht_perfmon status/start/stop/restart
ex: sudo  /etc/init.d/chtcollectd status
sudo  /etc/init.d/cht_perfmon start

  • Missing last_upload file?

    $ cat /var/lib/chtcollectd/last upload.txt

    Use this command to read the contents of the last_upload.txt and share the file to support. Please notify us if it is not present.

  • Retrieve the facter JSON response from Linux based agent instance

    $ /opt/cht_perfmon/embedded/bin/facter --json

  • Remove the old installation and install a new one manually upon customer approval

    • To Uninstall
        $ wget -O - https://s3.amazonaws.com/remote-collector/agent/uninstall_cht_perfmon.sh | sudo sh
    $ sudo rm -rf cht_agent_install/
    $ sudo rm -rf install_cht_perfmon.sh
    • To install
        $ wget https://s3.amazonaws.com/remote-collector/agent/v24/install_cht_perfmon.sh -O install_cht_perfmon.sh;
    $ sudo sh install_cht_perfmon.sh 24 <api_key> <cloud_name>;

  • Check if the user: cht_agent is available

    $ id cht_agent

  • If the cht_agent user is not configured correctly, delete the user and recreate them.

        $ userdel -r cht_agent - delete
    $ sudo useradd cht_agent
    $ chown -R cht_agent:cht_agent /opt/cht_perfmon
    $ sudo usermod -a -G docker cht_agent
    $ sudo usermod -a -G docker cht_agent
    $ cht_agent -m -U -G docker
    $ chgrp -R cht_agent /var/lib/chtcollectd/
    $ chmod -R g+ws /var/lib/chtcollectd/
    $ chown -R cht_agent:cht_agent /opt/cht_perfmon

    Try to restart the collectd and perfmon services.

        $ sudo  /etc/init.d/chtcollectd start
    $ sudo  /etc/init.d/cht_perfmon start

  • Get saved state point

        $ cat /opt/cht_perfmon/saved_state.json

  • Check EOL (end of the line) in collectd.conf There should be an extra empty line added at the end in collectd.conf and restart in case collectd is not started. Restart cht_pefmon and collectd, if above change is added.

  • When gathering the content of the collector output directory, and you see the ‘S’ character for cht_agent If you run ls -alR /var/lib/chtcollectd and it returns with the ‘S’ character, it is not the expected outcome. In that case, run the following command-

        $ chmod 2775 /var/lib/chtcollectd

After an hour, you should be able to see last_upload file. Please share the details from last_upload and last_docker_upload as well.

Aggregator File Format

Integrate with VMware Aria Operations

This integration collects cost and usage data from VMware Aria Operations (formerly vRealize Operations) and ingests it into Tanzu CloudHealth.

What is Aria Operations Integration for Tanzu CloudHealth

The Aria Operations Integration for Tanzu CloudHealth collects cost and usage data from Aria Operations and ingests it into Tanzu CloudHealth. In this integration, an adapter instance is deployed on the Aria Operations platform to monitor vCenter resources and publish information to Tanzu CloudHealth. The Tanzu CloudHealth platform consolidates your multi-cloud data on a single view, providing visibility into your vSphere-based private cloud data using Aria Operations and the public cloud data through Tanzu CloudHealth.

Install and Configure VMware Aria Operations Integration for Tanzu CloudHealth Adapter

Complete the following steps to set up the Aria Operations Integration for Tanzu CloudHealth.

Step 1: Define Role and Permissions for VMware Aria Operations

Follow the steps below to create a new role and assign the permissions.

  1. In the Tanzu CloudHealth platform, from the left menu, navigate to Setup > Admin > Role Documents.
  2. Click New Role Document. You can also copy one of the built-in role documents (Standard User, Administrator, or Power User) and modify the copy to create your own.
  3. Add user Name and Description.
  4. Select whether to Share the user with sub-organizations.
  5. From the left scrolling pane, select Data Center, and select the necessary permissions as given in the following table.
Data Center Required Permissions
Dashboard Read Datacenter Dashboard, Change Datacenter Dashboard
Reports > Cost > Machine Read Data Center Server Cost Report, Export Data Center Server Cost Report, Save Data Center Server Cost Report, Share Data Center Server Cost Report, Subscribe Data Center Server Cost Report
Reports > Cost > Current Read Data Center Cost Current Report, Export Data Center Cost Current Report, Save Data Center Cost Current Report, Share Data Center Cost Current Report, Subscribe Data Center Cost Current Report
Reports > Cost > Cost Driver Read Data Center Cost Driver Report, Export Data Center Cost Driver Report, Save Data Center Cost Driver Report, Share Data Center Cost Driver Report, Subscribe Data Center Cost Driver Report
Reports > Usage > Machine Read Data Center Server Usage Report, Export Data Center Server Usage Report, Save Data Center Server Usage Report, Share Data Center Server Usage Report,Subscribe Data Center Server Usage Report
Reports > Performance > Machine Read Data Center Server Performance Report, Export Data Center Server Performance Report, Save Data Center Server Performance Report, Share Data Center Server Performance Report,Subscribe Data Center Server Performance Report
Reports > Performance > Memory Read Data Center Memory Performance Report, Export Data Center Memory Performance Report, Save Data Center Memory Performance Report, Share Data Center Memory Performance Report, Subscribe Data Center Memory Performance Report
Assets Read Data Center Tag, Export Data Center Tag, Save Data Center Tag, Subscribe Data Center Tag, Read Data Center Server File System, Export Data Center Server File System, Save Data Center Server File System, Subscribe Data Center Server File System, Read Data Center Server Network Interface, Export Data Center Server Network Interface, Save Data Center Server Network Interface, Subscribe Data Center Server Network Interface, Read Data Center Server Block Device, Export Data Center Server Block Device, Save Data Center Server Block Device, Subscribe Data Center Server Block Device, Read Data Center Server CPU, Export Data Center Server CPU, Save Data Center Server CPU, Subscribe Data Center Server CPU, Read Data Center Server Usage Daily
Accounts Create Data Center Account, Read Data Center Account, Update Data Center Account, Delete Data Center Account, Export Data Center Account, Save Data Center Account, Subscribe Data Center Account, Tag Data Center Account
Machine Update Data Center Server, Read Data Center Server, Export Data Center Server, Save Data Center Server, Subscribe Data Center Server, Tag Data Center Server
Hosts / DataStores / Clusters / Datacenters Read Data Center Host, Export Data Center Host, Save Data Center Host, Subscribe Data Center Host, Tag Data Center Host
Agents Read Datacenter Agent Configuration, Update Datacenter Agent Configuration, Disable Autoupdate Datacenter Agent Status, Enable Autoupdate Datacenter Agent Status, Read Datacenter Agent Status, Export Datacenter Agent Status, Save Datacenter Agent Status, Subscribe Datacenter Agent Status

From the left scrolling pane, select Setup, and select the necessary permissions as given in the following table.

Setup Required Permissions
Profile Read Profile, Update Profile, Generate API Key Profile
  • The user API access key must be associated with a user having either a default Power User role or an Administrator role.
  • If you want to associate the user API access key with a user having a custom role, then create a new role, and add the necessary permissions.

Step 2: Download Aria Operations Integration for Tanzu CloudHealth Adapter

Download the vRealize Operations Integration for Tanzu CloudHealth PAK file from VMware Marketplace, and save the PAK file to a temporary folder on your local system. Please note that the Management Pack names may temporarily display the old names (vRealize Operations and CloudHealth) in the Marketplace portal. We will soon update them with the new names (VMware Aria Operations and Tanzu CloudHealth, respectively).

Note - The vRealize Operations Integration for Tanzu CloudHealth version 1.0.5 includes an updated Log4j version 2.17.0 to resolve the Log4j vulnerability.

Step 3: Install the Aria Operations Integration for Tanzu CloudHealth Adapter

Prerequisites

  • Ensure that the Aria Operations version is 8.2 and above. To check the current version, click the profile icon, and select About. If you need to upgrade the version, refer to Upgrade VMware Aria Operations instructions.
  • Ensure to use the Aria Operations instance with the disabled FIPS mode.
  • Set the Currency in Aria Operations to USD. To change the currency settings,
    • for Aria Operations On-premises setup- Click the Administration tab. From the left pane, go to Management > Global Settings > Currency.
    • for Aria Operations Cloud setup- From the left navigation pane, click Administration. Select Global currency. On the Global Settings page, select Cost/Price > Currency.

Follow these steps to install the adapter instance:

  1. Login to the Aria Operations Manager platform with administrative privileges.
  2. For the On-prem setup- Click the Administration tab. From the left pane, select Solutions > Repository. At the bottom of the Repository page, click Add/Upgrade.
    For the Cloud setup – From the left navigation pane, go to Data Sources > Integrations, and click the Repository tab. Click Add.
  3. Click the Administration tab. From the left pane, select Solutions > Repository. At the bottom of the Repository page click Add/Upgrade.
  4. In Select Solution, click Browse and select the downloaded PAK file
  5. Read and accept the ‘Install the PAK file even if it is already installed’ checkbox and click Upload. Installation details appear with a success message, The PAK file signature is valid. The upload might take several minutes to complete.
  6. Click Next.
  7. Accept the End User License Agreement by clicking the I accept the terms of this agreement checkbox and click Next.
  8. Finally, check the Installation Details and click Finish.

Step 4: Configure an Adapter Instance for the Aria Operations Integration for Tanzu CloudHealth

Best Practices

  • Do not add the Aria Operations Integration for Tanzu CloudHealth adapter, if the Cluster already has more than 80% CPU usage,
  • Do not configure Aria Operations Integration for Tanzu CloudHealth adapter at the same time when the Cost Engine job is scheduled, as these processes are also huge CPU consumers.

Prerequisite

If you use Aria Operations cloud setup and collector as a cloud proxy for this integration, upgrade the HAProxy buffer size. The default HAProxy configuration will not support the Virtual Machines collection. Therefore you need to upgrade the HAProxy buffer size using the following instructions.

  1. Update HAProxy configuration to set bufsize: vim /etc/haproxy/haproxy.cfg

  2. Add the following lines under the global section:

    global
  log localhost local0 info
  log localhost local1 info
  chroot /etc/haproxy
  ca-base /etc/ssl/certs
  crt-base /etc/ssl/private
  maxconn 32768
  tune.bufsize 65536

  3. Restart the HAProxy service service haproxy restart

Note

This prerequisite is applicable only for Aria Operations cloud setup and not required for on-premises setup.

Follow these steps to configure the Adapter instance:

  1. In the Aria Operations Manager console, click the Administration tab, and from the left navigation, select Repository.
  2. Scroll down to the Other Management Packs section, locate the vRealize Operations Integration for Tanzu CloudHealth, and click Add Account, or from the left navigation pane, go to Other Accounts and click Add Account.
  3. On the Account Types page, select VMware vRealize Operations Integration for Tanzu CloudHealth.
  4. On the New Account page, give a Name to your account and add a Description.
  5. Click + to add a new credential.
  6. In the Manage Credential dialog box, enter the friendly Credential name to identify the configured credentials and the Tanzu CloudHealth API key. The user API access key must be associated with either a default Power user or an Administrator role. For more information on how to generate a Tanzu CloudHealth API key, see the Authentication article.
  7. (Optional) Enter the following proxy details to set up the adapter instance with no internet access:
    • Proxy Host
    • Proxy Port
    • Proxy Username
    • Proxy Password
    • Proxy Domain
  8. Click Ok.
  9. On the New Account page, select Collector/Group upon which you want to run the adapter instance. A collector gathers objects into its inventory for monitoring. By default, it is set to the Default collector group for optimal data collection.
  10. Click Validate Connection to initiate the authentication request. This step ensures that the Aria Operations instance can reach Tanzu CloudHealth Graphql endpoint - https://apps.cloudhealthtech.com/graphql.
  11. After validation is successful, a success message appears on the screen. Click OK.
  12. Click Add. The newly created account appears on the Other Accounts page.

Manage the Aria Operations Integration for Tanzu CloudHealth

  • Do not create more than one account in VMware Aria Operations Manager. There should be only one instance configured in the VMware Aria Operations Manager console.
  • If the adapter instance has stopped collecting data for more than 7 days, change the default collection cycle to N days, where N is the number of days the collection was stopped. Update the config.property file before the first collection begins.
  • To update the account information, click the account name on the Other Accounts page.
  • To delete the account, go to the Repository page, select the vRealize Operations Integration for Tanzu CloudHealth pack, and click Uninstall.

View Aria Operations within the Tanzu CloudHealth Platform

You can deploy the VMware Aria Operations Integration for Tanzu CloudHealth adapter in one or more existing on-prem VMware Aria Operations instances. In the Tanzu CloudHealth platform, you can view all the adapter instance details that you installed on the vRealize Operations Manager console.

  1. Login to the Tanzu CloudHealth platform and click the Data Center tab.
  2. From the left pane, select Setup > Accounts > VMware Aria Operations.

View Adapter instance details in the CloudHealth platform

All the configured adapter instance details appears on the page.

View Tanzu CloudHealth logs in the Aria Operations Manager console

  1. In the VMware Aria Operations Manager console, from the left navigation pane, click Support, and select Logs.
  2. In the Logs pane, click the MASTER file, and go to Collector > Adapter > Tanzu CloudHealthHybridAdapter.

For FAQs on the Aria Operations Integration, see Tanzu CloudHealth Knowledge Base Article.

Troubleshoot the VMware Aria Operations Integration for Tanzu CloudHealth

Buffer Size Overflow Error

If you get a Bad Request or Invalid Request error, you can now update the number of resource IDs you provide while calling the GET /api/resources/properties API.

  1. Log in to the Aria Operations Manager instance platform using root credentials: ssh root@<vrops-instance-address>
  2. Enter the root password: vmware
  3. Navigate to the adapter config properties folder: cd /usr/lib/vmware-vcops/user/plugins/inbound/CloudHealthHybridAdapter/conf/
  4. Open config.properties file.
  5. Update the max.resources value. Ensure that the value should be less than 500.

Integrate with Aria Operations Management Pack

The VMware Aria Operations Management Pack for VMware Tanzu CloudHealth ingests public cloud costs from Tanzu CloudHealth into Aria Operations.

Benefits of Integrating with the Aria Operations Management Pack 

Using the Aria Operations Management Pack, you can:

  • Track public cloud infrastructure costs in Aria Operations
  • View the cost of multiple clouds in Aria Operations.
  • View the accounts, regions, services cost trends, and top spenders of the configured AWS, Azure and GCP accounts.
  • View the cost of Perspectives and groups defined by Tanzu CloudHealth in Aria Operations.

This Management Pack is part of a bi-directional integration between Tanzu CloudHealth and Aria Operations; giving users the flexibility to use their platform of choice to view multi-cloud costs. For information on the management pack that ingests data from Aria Operations into Tanzu CloudHealth, see Integrate with Aria Operations article.

Install and Configure Aria Operations Management Pack for Tanzu CloudHealth

To install and configure the Aria Operations Management Pack for Tanzu CloudHealth, see VMware Aria Operations for Integrations.

After creating a Tanzu CloudHealth integration, you can use the dashboards to view the accounts, regions, and services cost trends of the AWS, Azure and GCP accounts configured in this Management Pack.

Integrate with VMware Aria Automation

Integrating Tanzu CloudHealth with VMware Aria Automation provides deployment and project-level spending transparency, which gives you greater cost visibility and optimization.

Benefits of Integrating with Aria Automation

Aria Automation ingests Tanzu CloudHealth data to provide:

  • An overview and detailed view of the deployment price along with the price month-to-date value.
  • Pricing and cost information for public cloud deployments.
  • Cost history for public cloud deployments in Tanzu CloudHealth.
  • Current and historical price reports for public cloud deployments.

After integrating with Tanzu CloudHealth, you can also view the cost history for public cloud deployments directly in Tanzu CloudHealth. In the Tanzu CloudHealth platform, select the public cloud from the top menu for which you want to see the cost analysis. From the left menu, go to Reports > Cost and select History or Current. The cost analysis provides an overview of Perspective groups and their associated costs. For more information, see:

Prerequisites

  • At least one Perspective is available for reporting in Tanzu CloudHealth.
  • The Tanzu CloudHealth API key has Perspective CRUD Privileges, and AWS and Azure cost current and history report read privileges.

Configure Tanzu CloudHealth in Aria Automation

To configure Tanzu CloudHealth in Aria Automation, refer to Configure Tanzu CloudHealth Integration in Cloud Assembly.After creating a Tanzu CloudHealth integration, to view the pricing and cost information for public cloud deployments in Cloud Assembly, refer to How to view pricing for AWS and Azure.

  • It can take 12 hours for Tanzu CloudHealth to synchronize any new vRealize Automation deployments.After the initial synchronization, Tanzu CloudHealth generates the cost for all perspective groups and sends the data to vRealize Automation.
  • Currently, Cloud Assembly does not support pricing for GCP deployments.
check-circle-line exclamation-circle-line close-line
Scroll to top icon