DocumentationGrafana CloudMonitor infrastructureGrafana integrationsIntegrations referencevSphere

vSphere integration for Grafana Cloud

VMware vSphere is a virtualization platform that enables organizations to virtualize and consolidate their IT infrastructure, allowing multiple virtual machines (VMs) to run on a single physical server. It provides features such as resource pooling, high availability, and centralized management through vCenter Server, enhancing efficiency, flexibility, and scalability in data center environments. vSphere simplifies IT management, improves resource utilization, and delivers cost savings while ensuring reliability and performance for virtualized workloads.

This integration supports vCenter Server 7.0.2.x+ and ESXi 6.7 U2+.

This integration includes 5 useful alerts and 5 pre-built dashboards to help monitor and visualize vSphere metrics and logs.

Before you begin

Metrics

A “Read Only” user assigned to a vSphere is required. This user must have permissions to the vCenter server, cluster and all subsequent resources being monitored in order to retrieve information about them.

In order to capture key vSphere metrics, you must set your Statistics Collection Level to at least level 2 as described here.

The minimum version of Alloy which supports this integration is v1.2.0. Because the otelcol.receiver.vcenter component is still experimental in v1.2.0, you will need to run Alloy with the –stability.level=experimental flag.

Logs

In order to collect vCenter logs, they must be forwarded to a remote syslog server as described here. Alloy must be installed and configured to collect logs on the same server as the remote syslog server.

Install vSphere integration for Grafana Cloud

1. In your Grafana Cloud stack, click Connections in the left-hand menu.
2. Find vSphere and click its tile to open the integration.
3. Review the prerequisites in the Configuration Details tab and set up Grafana Agent to send vSphere metrics and logs to your Grafana Cloud instance.
4. Click Install to add this integration’s pre-built dashboards and alerts to your Grafana Cloud instance, and you can start monitoring your vSphere setup.

Configuration snippets for Grafana Alloy

Advanced mode

The following snippets provide examples to guide you through the configuration process.

To instruct Grafana Alloy to scrape your vSphere instances, manually copy and append the snippets to your alloy configuration file, then follow subsequent instructions.

Advanced integrations snippets

alloy Copy

otelcol.receiver.vcenter "integrations_vsphere" {
    endpoint = "https://<vcenter-hostname>:<vcenter-port>"
    username = "<vcenter-user>"
    password = "<vcenter-password>"

    tls {
        insecure = true
    }

    output {
        metrics = [otelcol.processor.batch.integrations_vsphere.input]
    }
}

otelcol.processor.batch "integrations_vsphere" {
    output {
        metrics = [otelcol.processor.transform.integrations_vsphere.input]
    }
}

otelcol.processor.transform "integrations_vsphere" {
    error_mode = "ignore"

    metric_statements {
        context = "resource"
        statements = [
            `set(attributes["job"], "integrations/vsphere") where attributes["job"] == nil`,
        ]
    }

    output {
        metrics = [otelcol.exporter.prometheus.integrations_vsphere.input]
    }
}

otelcol.exporter.prometheus "integrations_vsphere" {
    forward_to = [prometheus.remote_write.metrics_service.receiver]

    resource_to_telemetry_conversion = true
}

This integration uses the otelcol.receiver.vcenter component to collect VMware vSphere metrics from a vCenter Server. Configure the following properties according to your environment:

• endpoint: This must be set to the vCenter Server. The expected format is ://:.
• username: This must be set to the user used to collect metrics from the vCenter Server.
• password: This must be set to the password for the user used to collected metrics from the vCenter Server.
• tls: Here a user must set options based on the vCenter Server’s TLS configuration.

These metrics are first fed into the otelcol.processor.batch component to reduce the number of outgoing network requests required to transmit data.

Then they are fed into the otelcol.processor.transform component which will add a job label with a value of integrations/vsphere onto every metric.

Finally, the otelcol.exporter.prometheus component is used to convert the OTLP formatted metrics to Prometheus formatted metrics. Here OTEL resource attributes are converted to prometheus labels on each metric as well.

Advanced logs snippets

linux

alloy Copy

loki.source.syslog "integrations_vsphere" {
    forward_to = [loki.process.integrations_vsphere_drop.receiver]

    listener {
        address = "<vcenter-host>:<vcenter-syslog-port>"
        protocol = "tcp"
        use_rfc5424_message = true
        labels = {
            job = "integrations/vsphere",
        }
    }
}

loki.process "integrations_vsphere_drop" {
    forward_to = [loki.process.integrations_vsphere_labels.receiver]

    stage.regex {
        expression = "^<\\S+>\\S* \\d+-\\d+-\\d+T\\d+:\\d+:\\d+\\.\\d+Z (?<instance>\\S+) (?<log_type>\\S+) .*$"
    }

    stage.labels {
        values = {
            log_type = "",
            instance = "",
        }
    }

    stage.match {
        selector = "{log_type=~\".+\", log_type!=\"vpxd-main\", log_type!=\"vpxd-svcs-main\", log_type!=\"analytics\", log_type!=\"applmgmt\"}"
        action = "drop"

        drop_counter_reason = "vsphere_non_priority_logs"
    }
}

loki.process "integrations_vsphere_labels" {
    forward_to = [loki.write.grafana_cloud_loki.receiver]

    stage.match {
        selector = "{log_type=\"vpxd-main\"}"

        stage.regex {
            expression = "^.*vpxd-main \\S+ \\S+ \\S+ \\d+-\\d+-\\d+T\\d+:\\d+:\\d+\\.\\d+Z (?<level>\\w+)\\s+.*$"
        }

        stage.labels {
            values = {
                level = "",
            }
        }
    }

    stage.match {
        selector = "{log_type=\"vpxd-svcs-main\"}"

        stage.regex {
            expression = "^.*vpxd-svcs-main \\S+ \\S+ \\S+ \\d+-\\d+-\\d+T\\d+:\\d+:\\d+\\.\\d+Z \\[\\S+ \\[\\S*\\] (?<level>\\w+)\\s+.*$"
        }

        stage.labels {
            values = {
                level = "",
            }
        }
    }

    stage.match {
        selector = "{log_type=\"applmgmt\"}"

        stage.regex {
            expression = "^.+applmgmt \\S+ \\S+ \\S+ \\d+-\\d+-\\d+T\\d+:\\d+:\\d+ \\S+ \\S+ \\[\\S+\\](?<level>\\w+):.*$"
        }

        stage.labels {
            values = {
                level = "",
            }
        }
    }

    stage.match {
        selector = "{log_type=\"analytics\"}"

        stage.regex {
            expression = "^.*analytics \\S+ \\S+ \\S+ \\d+-\\d+-\\d+T\\d+:\\d+:\\d+\\.\\d+Z \\S+\\s+(?<level>\\w+)\\s+.*$"
        }

        stage.labels {
            values = {
                level = "",
            }
        }
    }

    stage.template {
        source = "level"
        template = "{{ ToLower .Value }}"
    }

    stage.labels {
        values = {
            "level" = "",
        }
    }
}

To monitor your VMware Appliance Management Service (applmgmt), VMware Analytics (analytics), and VMware vCenter Server (vpxd) logs, you will use a combination of the following components.

First the loki.source.syslog component defines where syslogs should be listened from and where to forward them to. Change the following properties according to your environment:

• address: The <host:port> corresponding with the vCenter Server’s remote syslog forwarding configuration. <vcenter-host> must match the vCenter Server’s IP address and <vcenter-syslog-port> must match the vCenter Server’s remote syslog forwarding configuration.
• protocol: Can be set to either tcp or udp.

Next the loki.process component defines how to process logs before sending them to Loki.

Dashboards

The vSphere integration installs the following dashboards in your Grafana Cloud instance to help monitor your system.

• vSphere clusters
• vSphere hosts
• vSphere logs
• vSphere overview
• vSphere virtual machines

vSphere overview

vSphere overview (hosts)

vSphere clusters

Alerts

The vSphere integration includes the following useful alerts:

Metrics

The most important metrics provided by the vSphere integration, which are used on the pre-built dashboards and Prometheus alerts, are as follows:

• up
• vcenter_cluster_cpu_effective
• vcenter_cluster_cpu_limit
• vcenter_cluster_host_count
• vcenter_cluster_memory_effective_bytes
• vcenter_cluster_memory_limit_bytes
• vcenter_cluster_vm_count
• vcenter_cluster_vm_template_count
• vcenter_datastore_disk_usage_bytes
• vcenter_datastore_disk_utilization_percent
• vcenter_host_cpu_usage_MHz
• vcenter_host_cpu_utilization_percent
• vcenter_host_disk_latency_avg_milliseconds
• vcenter_host_disk_throughput
• vcenter_host_memory_usage_mebibytes
• vcenter_host_memory_utilization_percent
• vcenter_host_network_packet_error_rate
• vcenter_host_network_packet_rate
• vcenter_host_network_throughput
• vcenter_host_network_usage
• vcenter_resource_pool_cpu_shares
• vcenter_resource_pool_cpu_usage
• vcenter_resource_pool_memory_shares
• vcenter_resource_pool_memory_usage_mebibytes
• vcenter_vm_cpu_usage_MHz
• vcenter_vm_cpu_utilization_percent
• vcenter_vm_disk_latency_avg_milliseconds
• vcenter_vm_disk_throughput
• vcenter_vm_disk_usage_bytes
• vcenter_vm_disk_utilization_percent
• vcenter_vm_memory_ballooned_mebibytes
• vcenter_vm_memory_swapped_mebibytes
• vcenter_vm_memory_usage_mebibytes
• vcenter_vm_memory_utilization_percent
• vcenter_vm_network_packet_drop_rate
• vcenter_vm_network_packet_rate
• vcenter_vm_network_throughput_bytes_per_sec
• vcenter_vm_network_usage

Changelog

md Copy

# 1.0.0 - July 2024

- Initial release

Cost

By connecting your vSphere instance to Grafana Cloud, you might incur charges. To view information on the number of active series that your Grafana Cloud account uses for metrics included in each Cloud tier, see Active series and dpm usage and Cloud tier pricing.