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.
What to administer
Once the Splunk for VMware Solution is installed you will have administration tasks to perform to keep your environment up to date. If you add, remove, or change any of the resources in your environment ,you will re-configure the Solution to reflect those changes.
Changes to engine.conf
Some resource changes that will require configuration changes in engine.conf are:
- A new forwarder appliance (FA) is installed
- One or more ESX/i hosts or vCenter servers are added or removed, and they are monitored by an FA
- One or more ESX/i hosts or vCenter servers have changed their log-in information.
Changes to inputs.conf
To scale up the Solution to run multiple engine instances in your environment you will configure inputs.conf . You may need to add, remove, or update stanzas in the inputs.conf file in the following situations:
- A new forwarder appliance (FA) is freshly installed
- One or more engine instances are added or removed in order to scale up / down the solution
Last modified on 10 January, 2013
| Auto load balancing | Access permissions and credentials |
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
Download manual
Feedback submitted, thanks!