A Go tool that collects VMware vSphere, vCenter, and ESXi performance metrics and sends them to InfluxDB for monitoring and visualization.
vsphere-influxdb-go is a tool written in Go that collects performance metrics from VMware vSphere, vCenter, and ESXi environments and sends them to InfluxDB. It solves the problem of monitoring and analyzing VMware infrastructure performance by providing a customizable, efficient way to gather data for capacity planning, debugging, and visualization.
System administrators, DevOps engineers, and IT professionals managing VMware-based infrastructures who need detailed performance monitoring and capacity planning capabilities.
Developers choose vsphere-influxdb-go for its comprehensive metric collection, efficiency in handling large environments, and seamless integration with InfluxDB and Grafana, enabling tailored monitoring without relying on proprietary solutions.
Collect VMware vSphere, vCenter and ESXi performance metrics and send them to InfluxDB
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Collects all possible performance metrics from vCenters and ESXi, including hosts, clusters, resource pools, datastores, and VMs, as detailed in the project description.
Capable of handling large infrastructures, such as 30 vCenters, 100 ESXi, and 1400 VMs, in under 30 seconds, as demonstrated in the crontab example.
Supports JSON configuration files and environment variables, enabling easy setup for various deployments, including containerized environments.
Available as packages for Linux, Darwin, Windows, and FreeBSD on multiple architectures, ensuring broad compatibility across systems.
Currently, only one vCenter/ESXi server can be configured via environment variables, restricting containerized deployments for multi-server environments.
Requires adjusting vSphere performance counter levels manually using external scripts, adding complexity to the setup process.
Lacks built-in daemonization, service discovery, and a ready Dockerfile, as noted in the TODO list, necessitating additional work for production use.