vSphere with Tanzu using NSX-T - Part34 - CPU and Memory utilization of a supervisor cluster

vSphere with Tanzu is a Kubernetes-based platform for deploying and managing containerized applications. As with any cloud-native platform, it's essential to monitor the performance and utilization of the underlying infrastructure to ensure optimal resource allocation and avoid any potential issues. In this blog post, we'll explore a Python script that can be used to check the CPU and memory allocation/ usage of a WCP Supervisor cluster.

You can access the Python script from my GitHub repository: https://github.com/vineethac/VMware/tree/main/vSphere_with_Tanzu/wcp_cluster_util

Sample screenshot of the output

The script uses the Kubernetes Python client library (kubernetes) to connect to the Supervisor cluster using the admin kubeconfig and retrieve information about the nodes and their resource utilization. The script then calculates the average CPU and memory utilization across all nodes and prints the results to the console.

Note: In my case instead of running it as a script every time, I made it an executable plugin and copied it to the system executable path. I placed it in $HOME/.krew/bin in my laptop.

Hope it was useful. Cheers!

vRealize Operations Manager 7.5 - Part10 - Adding Remote Collector Node

In this article, I will briefly explain the configuration of a remote collector node and a sample scenario too.

Note: Before adding the remote collector nodes a vROps master node should be present.

Refer to my previous blogs for the installation and configuration of the vROps master node and enabling high availability. Here I have a single node vROps 7.5 instance which is a master and I will be expanding it with a remote collector node.

Consider the following scenario:

Datacenter A is the head office where the vROps master is installed. Datacenter B and C need to be monitored using the vROps instance configured at Datacenter A. In this case, Remote Collector nodes are installed at Datacenter B and C. As per VMware recommendation the latency between sites should be 200ms or less. 

Refer vROps 7.5 reference architecture for recommendations from VMware on different deployment profiles and other best practices. 

Deploy a vROps instance at the remote location and open its management IP address in a web browser. 

Click on Expand an existing installation.

Click Next.

Provide a name for the collector node and select node type Remote Collector.

Enter IP of vROps master node and click Validate.

Click Next.

Provide cluster admin password and click Next.

Click Finish.

This may take around 6-8 minutes to complete.

Select Finish adding new nodes.

Click OK.

The remote collector is now part of the cluster.

Now log in to the master vROps instance.
Select Administration > Management > Collector Groups.
You can see only the master node is part of the Default collector group.
Click Create collector Group (+).

Provide a name and select the remote collector node.

Now you can see the remote collector node is part of the newly created collector group.

Now, we will add a vCenter Adapter instance that will monitor the vCenter server of the remote site using the newly added remote collector node.

Click Administration > Solutions > Configuration > VMware vSphere.
Click Configure (gear icon).

Click (+) to add a new vCenter adapter and provide the necessary details.

In the advanced settings, select the collector group.

Click Test connection, Accept and save settings. 

Click OK.

Verify the collection state and status.

Hope it was useful. Cheers.

Related posts

vRealize Operations Manager 7.5 - Part1 - Installation

vRealize Operations Manager 7.5 - Part2 - Configure vCenter adapter and dashboards overview

vRealize Operations Manager 7.5 - Part3 - Rightsizing

vRealize Operations Manager 7.5 - Part4 - High availability

vRealize Operations Manager 7.5 - Part5 - Alerting

vRealize Operations Manager 7.5 - Part6 - Adding new symptoms and alert definitions

vRealize Operations Manager 7.5 - Part7 - vSAN monitoring and troubleshooting

vRealize Operations Manager 7.5 - Part8 - Super Metrics

vRealize Operations Manager 7.5 - Part9 - Dashboard sharing

vRealize Operations Manager 7.5 - Part8 - Super Metrics

In this article, I will briefly explain about using super metrics in vROps 7.5. For example, I will take the VM NUMA optimization super metric which was released recently. You can download the super metric JSON file from the VMware sample exchange. 

Once the JSON file is downloaded, login to your vROps instance. Navigate to Administration - Configuration and select Super Metrics. Click on Import Super Metric.

Browse and select the JSON super metric file that you downloaded. Click DONE.

Once it is done, you can see the two super metrics. 

To enable the super metric in a policy:

Select the super metric - Edit Selected Super Metric - Goto Enable in a Policy  - Select vSphere Solution's Default Policy and click FINISH.

Now after the default collection interval, you can see the super metric tab as shown below. 

As you can see in the above screenshot, for this virtual machine "lustre01", recommendations are: 

• NUMA optimal CPU socket: 1 
• NUMA optimal CPU cores per socket: 8

Hope it was useful. Cheers!

References

https://vmspot.com/enabling-super-metrics-in-vrops/

Related posts

vRealize Operations Manager 7.5 - Part7 - vSAN monitoring and troubleshooting

vRealize Operations Manager 7.5 - Part6 - Adding new symptoms and alert definitions

vRealize Operations Manager 7.5 - Part5 - Alerting

vRealize Operations Manager 7.5 - Part4 - High availability

vRealize Operations Manager 7.5 - Part3 - Rightsizing

vRealize Operations Manager 7.5 - Part2 - Configure vCenter adapter and dashboards overview

vRealize Operations Manager 7.5 - Part1 - Installation