Documentation

Monitor vSphere

Use the vSphere Dashboard for InfluxDB v2 template to monitor your vSphere host. First, apply the template, and then view incoming data. This template uses the Docker input plugin to collect metrics stored in InfluxDB and display these metrics in a dashboard.

The Docker Monitoring template includes the following:

Apply the template

  1. Use the influx CLI to run the following command:

    influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/vsphere/vsphere.yml
    

    For more information, see influx apply.

    Ensure your influx CLI is configured with your account credentials and that configuration is active. For more information, see influx config.

  2. Install Telegraf on a server with network access to both the vSphere host and InfluxDB v2 API.

  3. In your Telegraf configuration file (telegraf.conf), do the following:

    • Set the following environment variables:
      • INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the telegraf bucket. See how to view tokens.
      • INFLUX_ORG: Name of your organization. See how to view your organization.
      • INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.
      • INFLUX_BUCKET: Bucket to store data in. To use the bucket included, you must export the variable: export INFLUX_BUCKET=vsphere
    • Set the host address to the vSphere and provide the username and password as variables:
      vcenters = [ "https://$VSPHERE_HOST/sdk" ]
      username = "$vsphere-user"
      password = "$vsphere-password"
      
  4. Start Telegraf.

View incoming data

  1. In the InfluxDB user interface (UI), select Dashboards in the left navigation.

  2. Open the vsphere dashboard to start monitoring.


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud powered by TSM