Use this topic to learn the deployment details and configurations of your Tanzu Application Platform Telemetry (commonly known as TAP Telemetry).
The installation creates the following in your Kubernetes cluster:
tap-telemetry
.informer
, and a corresponding secret for the service account. This secret is bound to a ClusterRole named tap-telemetry-admin
.tap-telemetry-informer
to retrieve the deployment ID, which is sent as sender ID in heartbeat metrics.tap-telemetry-informer-admin
that binds the informer
service account to the tap-telemetry-informer
role.tap-telemetry-admin
that has access to each Tanzu Application Platform component to gather information from.tap-telemetry-informer-admin
that binds the informer
service account to the tap-telemetry-informer
cluster role.customer_entitlement_account_number
is the unique identifier to differentiate between the data from your cluster and the data from other clusters. You can configure this property in your tap-telemetry-values.yaml
:
customer_entitlement_account_number: "12345"
It creates a config map named vmware-telemetry-identifiers
in the vmware-system-telemetry
namespace, which is used internally to log your information.
Repeat these steps for the Build, Run, and View Cluster. For more information, see Install multicluster Tanzu Application Platform profiles.