You can use the vSphere UI to get a high-level view of events in your Tanzu Kubernetes clusters, and you can use the CLI to see very detailed information. Neither of these is both comprehensive and easy though. If you have onboarded your vSphere 8 with Tanzu installation to Tanzu Mission Control (TMC) (see my previous post, Registering a vSphere 8 with Tanzu Supervisor Cluster with Tanzu Mission Control, and allowed TMC to manage your Tanzu Kubernetes clusters (see my previous post, Managing a vSphere 8 with Tanzu Workload Cluster in Tanzu Mission Control), you are incredibly close to having true observability for your environment.
In the TMC UI, while the workload cluster is displayed, click the Actions dropdown menu and then click on the Tanzu Observability sub-menu.
Click the Add… menu item.
If you’ve performed this operation before you can select your credential from the list of existing credentials and skip past the next few steps. Otherwise, click the Setup New Credential link.
Provide the appropriate Aria Operations for Applications URL and your API token. Click the Confirm button.
In the Integrations pane for the TKGS cluster Overview page, Tanzu Observability is now listed and the TMC Adapter status is Attention. If you click on the exclamation point, you’ll see that this is expected.
You should see that a new namespace named tanzu-observability-saas was very recently created.
kubectl get ns tanzu-observability-saas NAME STATUS AGE tanzu-observability-saas Active 26s
And there are several familiar resources being created in this namespace.
kubectl -n tanzu-observability-saas get all NAME READY STATUS RESTARTS AGE pod/tmc-wavefront-operator-554ff9c7b7-hnzg5 1/1 Running 0 55s pod/wavefront-collector-nql7v 1/1 Running 0 49s pod/wavefront-collector-pdckb 1/1 Running 0 49s pod/wavefront-proxy-tanzu-6d8868985c-x4fqq 0/1 ContainerCreating 0 18s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/wavefront-proxy-tanzu ClusterIP 10.99.101.164 <none> 2878/TCP,9411/TCP 49s NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE daemonset.apps/wavefront-collector 2 2 2 2 2 <none> 49s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/tmc-wavefront-operator 1/1 1 1 55s deployment.apps/wavefront-proxy-tanzu 0/1 1 0 18s NAME DESIRED CURRENT READY AGE replicaset.apps/tmc-wavefront-operator-554ff9c7b7 1 1 1 55s replicaset.apps/wavefront-proxy-tanzu-6d8868985c 1 1 0 18s
Eventually, the TMC Adapter status of the Tanzu Observability integration will change to OK.
And all resources in the tanzu-observability-saas namespace should be in a running state.
kubectl -n tanzu-observability-saas get all NAME READY STATUS RESTARTS AGE pod/tmc-wavefront-operator-554ff9c7b7-hnzg5 1/1 Running 0 3m51s pod/wavefront-collector-nql7v 1/1 Running 0 3m45s pod/wavefront-collector-pdckb 1/1 Running 0 3m45s pod/wavefront-proxy-tanzu-6d8868985c-x4fqq 1/1 Running 0 3m14s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/wavefront-proxy-tanzu ClusterIP 10.99.101.164 <none> 2878/TCP,9411/TCP 3m45s NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE daemonset.apps/wavefront-collector 2 2 2 2 2 <none> 3m45s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/tmc-wavefront-operator 1/1 1 1 3m51s deployment.apps/wavefront-proxy-tanzu 1/1 1 1 3m14s NAME DESIRED CURRENT READY AGE replicaset.apps/tmc-wavefront-operator-554ff9c7b7 1 1 1 3m51s replicaset.apps/wavefront-proxy-tanzu-6d8868985c 1 1 1 3m14s
Very shortly thereafter, you should be able to see metrics coming in to Aria Operations for Applications.
Note the filter at the top that is displaying per-cluster information. When you have multiple clusters sending logs to Aria Operations for Applications, you can easily switch between them.