Splunk® App for VMware (Legacy)

Release Notes

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.

Known issues in Splunk App for VMWare 3.3.0

Publication date Defect number Description
2016-03-29 VMW-4218 Entity context is not being passed to the different detail pages.
2016-06-13 VMW-4311 VMware App - HTML dashboards broken.
2016-06-16 VMW-4312 Search head supporting VMware app is crashing.
2016-06-16 VMW-4302 VMware App fails initial license check.
2016-07-08 VMW-4319 Vmware app fails to connect to one vcenter , breaks all previously successfully connected vcenters.
2016-07-09 VMW-4320 Certification validation is disabled.
2016-07-09 VMW-4321 Sensitive Data Stored in Log Files
2016-07-09 VMW-4322 Log forging
2016-08-04 VMW-4358 Indexers without SA-Hydra and SA-Utils will sometimes be unable to initialize modular input "ta_vmware_collection_worker".
Last modified on 03 October, 2016
How to get help with Splunk App for VMWare   Fixed issues in Splunk App for VMWare 3.3.0

This documentation applies to the following versions of Splunk® App for VMware (Legacy): 3.3.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