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.
Download topic as PDF
engine.template
vcuser= vcpwd= vc= hostuser= hostpwd= host_csv= perfInstanceData=OFF ################################################################ #### FILL IN VALUES ABOVE. REPEAT ALL ENTRIES TO ADD ANOTHER VC-HOSTS SET. #### WORKS ON UPTO ABOUT 30HOSTS. MORE THAN THAT REQUIRES BEEFIER HARDWARE FOR THE FA OR #### DISTRIBUTION OF GENERATED .CONF FILES ACROSS FA's #### (THOUGH FA HOSTNAME'S IN .CONF FILES WILL NEED TO BE UPDATED #### AND INPUT.CONF FILES WILL NEED TO BE UPDATED TOO AS PER GUIDELINES IN DOCS). # EXAMPLE: #vcuser=Administrator #vcpwd=abc123 #vc=10.160.14.241 #hostuser=root #hostpwd=abc123 #host_csv=10.160.14.51,10.160.14.52,10.160.14.53,10.160.14.54,10.160.14.56 #perfInstanceData=OFF (or ON) #vcuser=Administrator #vcpwd=abc123 #vc=10.160.114.241 #hostuser=root #hostpwd=abc123 #host_csv=* #perfInstanceData=OFF (or ON) #USE WILDCARD TO RETRIEVE ALL MANAGED HOSTS #NOTE: UNMANAGED HOSTS MUST BE COMPILED MANUALLY AFTER THE ENGINEBUILDER IS RUN. CREATE THE UNMANAGED HOSTS' ENGINE.CONF FILES AS PER DOCS AND UPDATE INPUTS.CONF ################################################################
Last modified on 19 September, 2012
PREVIOUS engine.conf settings |
NEXT engine.conf.spec file |
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
Feedback submitted, thanks!