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 (EOL).
For documentation on the most recent version, go to the latest release.
Fixed problems
1.0.2 Fixes
All issues resolved in 1.0.2 are listed here.
- Engine stops sending cluster performance data with source=ClusterComputeResourcePerf and perftype=clSvcs (SOLNVMW-2178).
- vm_snapshots view should show "Approx. Delete Time" correctly when checkbox "Also display deleted snapshots" is enabled in the middle panel (SOLNVMW-2182).
- TimeInvSnapshot lookup does not store _time which causes the deleted notion of snapshots to be highly dependent on the frequency of inventory data (SOLNVMW-2181).
- Do not use host names in engine.conf. (SOLNVMW-1949). The workaround is to use fully qualified domain names for VMware servers.
- In large environments inventory related summary lookups can take up large amounts of memory. If this happens, please contact Splunk support for assistance (SOLNVMW-1948).
- Some multi-line log files may be parsed incorrectly (SOLNVMW-1900).
- The
logincreatortool does not work with existing local users on vCenter Server (SOLNVMW-1893). - In the ESX/i Log Browser view for vobd related logs, messages can be displayed incorrectly in the Object field (SOLNVMW-1892).
Last modified on 16 October, 2012
| Known issues and workarounds |
This documentation applies to the following versions of Splunk® App for VMware (EOL): 1.0.2
Download manual
Feedback submitted, thanks!