Telemetry can be deployed to any availability zone and subnet.
If enabled, telemetry data is kept on disk, but not sent. To learn more about what data is collected and how to access it, see What data is collected.
A VMware-issued API key is used to send telemetry. It can be obtained by contacting Tanzu Support.
The categorization of the environment: sandbox, pre-production, development, QA, or production.
You can optionally provide a nickname for your foundation. If it is specified, it is sent to VMware for identification purposes in reporting.
You can optionally configure skipping TLS verification for data collection from Tanzu Operations Manager.
There are two possible options that you can select, and you must select at least one, but can select both:
The first option is Operational Data which enables collection of consumption data only (these data would include Usage Service and Core Consumption). The Usage Service data from Tanzu Application service includes data such as App, Task, and Service Instance usage; TAS must be installed with the usage service errand enabled for this option to be selected
For more information on the Tanzu Application Service Usage Service data, please visit the documentation.
The second option is CEIP Data which enables collection of configuration and other usage data (eg. Opsmanager Data, Tile data, etc).
You can optionally configure skipping TLS verification for data collection of Usage Service.
Use Tanzu Operations Manager proxy settings, or override with your own (usable for HTTP, HTTPS, and No proxy).