Installing the Host Agent on VMware Tanzu
TABLE OF CONTENTS
|VMware Tanzu Application Service for VMs, formerly known as Pivotal Application Service (PAS)||2.3 through 2.10|
|Pivotal Isolation Segment||2.6 through 2.10|
|Pivotal Container Service (PKS)||1.5 trough 1.7|
|MySQL for VMware Tanzu||2.5.3 and above|
|RabbitMQ for VMware Tanzu||1.17.0 and above|
|Redis for VMware Tanzu||2.0.0 and above||On-demand service offering|
|MongoDB Enterprise Service for VMware Tanzu||1.13.0 and above|
Note: This page is relevant for you only if you use VMware Tanzu (formerly known as Pivotal Platform and Pivotal Cloud Foundry), as opposed to open source Cloud Foundry or pretty much any other Kubernetes-based technology. If you are using open source Cloud Foundry or any other deployments directly on BOSH, see our Installing the Instana Agent on BOSH docs.
The Instana agent is packaged for VMware Tanzu as a tile, which is packaged software that can be integrated into VMware Tanzu. Operators install tiles on their VMware Tanzu foundations, and developers use these services once they are installed.
The Instana tile, called "Instana Microservices Application Monitoring for VMware Tanzu", is available from VMware Tanzu Network. It provides full automation in deploying and managing the Instana agent across an entire VMware Tanzu foundation, including service instances spawned by other tiles, see Supported Versions for more information.
For information on how to download and install the Instana tile, see the VMware Tanzu documentation website.
The Instana tile is automatically configured to use
APM licenses on Diego cells (the hosts in your foundation that run your Cloud Foundry applications) and worker nodes of PKS clusters, and
INFRASTRUCTURE licenses everywhere else.