Splunk® App for VMware (Legacy)

Installation and Configuration Guide

On August 31, 2022, the Splunk App for VMware will reach its end of life. After this date, Splunk will no longer maintain or develop this product. The functionality in this app is migrating to a content pack in Data Integrations. Learn about the Content Pack for VMware Dashboards and Reports.
This documentation does not apply to the most recent version of Splunk® App for VMware (Legacy). For documentation on the most recent version, go to the latest release.

Clone the FA VM template

  1. Clone the FA VM template into as many specific FAs as you need to cover all of the ESX/i hosts in the environment.
  2. Configure each FA to gather time, performance, and log data by editing the engine.conf file.
  1. Important: Do NOT configure the engine.conf file to gather vCenter data for these VMs. This is only done in the first FA.
  2. Once you have created the FA VM clones, check that all the data you want to collect is coming into Splunk from the vCenter and the ESX/i hosts managed by your vCenter machines. You can view the data you are collecting in the Splunk App for VMware. Open the App and look at the health views to see that data collection is working correctly.


If you have multiple VC machines, you can repeat these steps to monitor each vCenter and the ESX/i hosts it manages,

Last modified on 04 September, 2012
Save the VM as a template   Your environment

This documentation applies to the following versions of Splunk® App for VMware (Legacy): 1.0, 1.0.1, 1.0.2, 1.0.3, 2.0


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters