Vcenter Integration with KloudMate

in today’s dynamic it environments, effective monitoring and management of virtualized resources are crucial for maintaining performance and reliability this document outlines the integration of vcenter with opentelemetry (otel), facilitating the collection and transmission of metrics from vmware vsphere environments, including both vcenter and esxi hosts by leveraging the vsphere apis, our integration allows seamless fetching of vital metrics, which are then forwarded to kloudmate this ensures that teams have access to real time insights and analytics, enabling proactive management of virtual infrastructure through this integration, organizations can enhance visibility into their virtualized resources, optimize performance, and streamline troubleshooting processes, ultimately driving improved operational efficiency pre requisites vcenter must be running with the version 8 and 7 0 user credentials a “read only” user assigned to a vsphere with permissions to the vcenter server, cluster and all subsequent resources being monitored must be specified in order for the receiver to retrieve information about them endpoint endpoint to the vcenter server or esxi host that has the sdk path enabled install the opentelemetry collector on the specific server which have access to vcenter check installing and configuring opentelemetry collector step 1 configure the receivers to scrape metrics as well as logs to start monitoring with vmware with otel collector, you need to configure vcenter receiver vcenter receiver linux users open the file located at /etc/otelcol contrib/config yaml /etc/otelcol contrib/config yaml using your preferred text editor windows users create a new file called config yaml config yaml in the c \program files\opentelemetry collector c \program files\opentelemetry collector folder you can use notepad or any text editor to do this add the suitable extensions extensions health check pprof endpoint 0 0 0 0 1777 zpages endpoint 0 0 0 0 55679 in this configuration file, ensure the vcenter receiver is set up to collect and send metrics according to your specific requirements receivers vcenter endpoint http //localhost 15672 #endpoint to the vcenter server or esxi host example format is \<protocol> //\<hostname> username \<username> # change username password \<password> #change password collection interval 1m initial delay 1s tls insecure true metrics vcenter host cpu utilization enabled false step 2 set up the processor component to identify resource information and either append or replace the resource values in the telemetry data with this information processors batch send batch size 5000 timeout 10s resourcedetection detectors \[system] system resource attributes host name enabled true host id enabled true os type enabled false resource attributes \ key service name action insert from attribute host name step 3 configure the exporter, extension and save the configuration set up the kloudmate backend on the exporter part of the open telemetry configuration file and configure the pipeline exporters debug verbosity detailed otlphttp endpoint 'https //otel kloudmate com 4318' headers authorization xxxxxxxx # use the auth key service pipelines metrics receivers \[vcenter] processors \[batch, resourcedetection, resource] exporters \[debug, otlphttp] extensions \[health check, pprof, zpages] step 4 to restart and verify the status of the opentelemetry (otel) collector, follow these steps for linux execute the following commands sudo systemctl restart otelcol contrib sudo systemctl status otelcol contrib these commands will restart the otel collector and display its current status for windows open the services window press win + r win + r , type services msc services msc , and press ok ok alternatively, search for " services services " in the windows start menu in the services window, locate the " opentelemetry collector opentelemetry collector " service right click the service and select " restart restart " subsequently, monitor the metrics on the kloudmate dashboard and set up an alarm to receive notifications if the potential metrics for a specific application rise default metrics metrics description vcenter datacenter cluster count the number of clusters in the datacenter vcenter datacenter host count the number of hosts in the datacenter vcenter datacenter vm count the number of vm's in the datacenter vcenter datacenter datastore count the number of datastores in the datacenter vcenter datacenter disk space the amount of available and used disk space in the datacenter vcenter datacenter cpu limit the total amount of cpu available to the datacenter vcenter datacenter memory limit the total amount of memory available to the datacenter vcenter cluster cpu limit the amount of cpu available to the cluster vcenter cluster cpu effective the effective cpu available to the cluster this value excludes cpu from hosts in maintenance mode or are unresponsive vcenter cluster memory limit the available memory of the cluster vcenter cluster memory effective the effective available memory of the cluster vcenter cluster vm count the number of virtual machines in the cluster vcenter cluster vm template count the number of virtual machine templates in the cluster vcenter cluster host count the number of hosts in the cluster vcenter cluster vsan throughput the vsan throughput of a cluster vcenter cluster vsan operations the vsan iops of a cluster vcenter cluster vsan latency avg the overall cluster latency while accessing vsan storage vcenter cluster vsan congestions the congestion of ios generated by all vsan clients in the cluster vcenter datastore disk usage the amount of space in the datastore vcenter datastore disk utilization the utilization of the datastore vcenter host cpu utilization the cpu utilization of the host system vcenter host cpu usage the amount of cpu used by the host vcenter host cpu capacity total cpu capacity of the host system vcenter host cpu reserved the cpu of the host is reserved for use by virtual machines vcenter host disk throughput average number of kilobytes read from or written to the disk each second vcenter host disk latency avg the latency of operations to the host system's disk vcenter host disk latency max highest latency value across all disks used by the host vcenter host memory utilization the percentage of the host system's memory capacity that is being utilized vcenter host memory usage the amount of memory the host system is using vcenter host network throughput the amount of data that was transmitted or received over the network by the host vcenter host network usage the sum of the data transmitted and received for all the nic instances of the host vcenter host network packet error rate the rate of packet errors transmitted or received on the host network vcenter host network packet rate the rate of packets transmitted or received across each physical nic (network interface controller) instance on the host vcenter host network packet drop rate the rate of packets dropped across each physical nic (network interface controller) instance on the host vcenter host vsan throughput the vsan throughput of a host vcenter host vsan operations the vsan iops of a host vcenter host vsan latency avg the host latency while accessing vsan storage vcenter host vsan congestions the congestion of ios generated by all vsan clients in the host vcenter host vsan cache hit rate the host's read ios which could be satisfied by the local client cache vcenter resource pool memory usage the usage of the memory by the resource pool vcenter resource pool memory shares the amount of shares of memory in the resource pool vcenter resource pool memory swapped the amount of memory that is granted to vms in the resource pool from the host's swap space vcenter resource pool memory ballooned the amount of memory in a resource pool that is ballooned due to virtualization vcenter resource pool memory granted the amount of memory that is granted to vms in the resource pool from shared and non shared host memory vcenter resource pool cpu usage the usage of the cpu used by the resource pool vcenter resource pool cpu shares the amount of shares of cpu in the resource pool vcenter vm memory ballooned the amount of memory that is ballooned due to virtualization vcenter vm memory usage the amount of memory that is used by the virtual machine vcenter vm memory swapped the portion of memory that is granted to this vm from the host's swap space vcenter vm memory swapped ssd the amount of memory swapped to fast disk device such as ssd vcenter vm disk usage the amount of storage space used by the virtual machine vcenter vm disk utilization the utilization of storage on the virtual machine vcenter vm disk latency avg the latency of operations to the virtual machine's disk vcenter vm disk latency max the highest reported total latency (device and kernel times) over an interval of 20 seconds vcenter vm disk throughput average number of kilobytes read from or written to the virtual disk each second vcenter vm network throughput the amount of data that was transmitted or received over the network of the virtual machine vcenter vm network packet rate the rate of packets transmitted or received by each vnic (virtual network interface controller) on the virtual machine vcenter vm network packet drop rate the rate of transmitted or received packets dropped by each vnic (virtual network interface controller) on the virtual machine vcenter vm network usage the network utilization combined transmit and receive rates during an interval vcenter vm cpu utilization the cpu utilization of the vm vcenter vm cpu usage the amount of cpu used by the vm vcenter vm cpu readiness percentage of time that the virtual machine was ready, but could not get scheduled to run on the physical cpu vcenter vm memory utilization the memory utilization of the vm vcenter vm vsan throughput the vsan throughput of a virtual machine vcenter vm vsan operations the vsan iops of a virtual machine vcenter vm vsan latency avg the virtual machine latency while accessing vsan storage for full details on metrics, click here