As an infrastructure operator in VMware Tanzu Mission Control, you can implement observability on a cluster group, which installs the collector on a set of clusters to enable them to start sending data to your Wavefront account.
After observability has been enabled for your organization, you can then add the clusters that you want to monitor in Wavefront. When you implement observability on a cluster group, Tanzu Mission Control pushes that out to each cluster in the group that isn't already added to Tanzu Observability. On each cluster that you add to Tanzu Observability, an extension is installed to collect and send metrics data in regular intervals (by default, every 60 seconds). Any clusters that have individually been added to Tanzu Observability are marked as overrides, and are not included in the cluster group integration.
Log in to the Tanzu Mission Control console.
- To edit the configuration of a cluster group, you must be associated with the clustergroup.edit role on the cluster group.
- To add the clusters in a cluster group to Tanzu Observability by Wavefront, you must be associated with the cluster.admin role on each cluster.
- To use an existing Tanzu Observability credential, you must be associated with the credential.view role on the credential.
For more information about Tanzu Observability credentials, see Create a Tanzu Observability Credential Object.
- In the Tanzu Mission Control console, navigate to the cluster group that you want to add to Tanzu Observability.
- On the cluster group detail page, click the Integrations tab.
- Click the Actions dropdown menu, and then choose Tanzu Observability by Wavefront > Add.
- In the Add dialog, select the Tanzu Observability credential to use to attach to your Wavefront account.
- Click Confirm.
When you click Confirm, Tanzu Mission Control installs an extension on each cluster in the cluster group to collect data from the cluster and send it to your Wavefront account in regular intervals. It might take several minutes before the collector is installed and running on each of the clusters in the cluster group.