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.
Fixed issues in Splunk App for VMWare 3.1.3
| Publication Date | Defect number | Description |
| 2014-12-18 | TAG-8885 | reliability: intermittent timestamp parsing errors from ta_vmware_collection_worker.py |
| 2014-12-18 | TAG-8886 | reliability: intermittent errors with "could not refresh the hydra health conf for node" |
| 2014-12-18 | TAG-8887 | reliability: intermittent errors from Splunk_TA_vmware/bin/ta_vmware_collection_scheduler.py |
| 2014-12-18 | TAG-8889 | reliability: intermittent errors with "local.meta: Refused forced reload: outstanding write" |
| 2014-12-18 | SOLNVMW-3874 / TAG-8265 | License term reported as unlimited when pointing to a remote master with a trial license. |
Last modified on 18 December, 2014
| Known issues in Splunk App for VMWare 3.1.3 | Credits |
This documentation applies to the following versions of Splunk® App for VMware (Legacy): 3.1.3
Download manual
Feedback submitted, thanks!