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.

Fixed issues in Splunk App for VMWare

Publication date Defect number Description
2016-05-06 VMW-4270 Vmware license check page fails to find valid license - App temporarily fails to load.
2016-06-09 VMW-4306 VMWare API data not showing after upgrade to 6.4.1.
2016-07-08 VMW-4321 Sensitive data stored in log files.
2016-07-13 VMW-4323 VMWare App continually showing license exceeded.
2016-07-20 VMW-4339 VMware Inventory and Performance raw data mismatch for Virtual Machine Ids.
2016-08-10 VMW-4364 ta_vmware_hierarchy_agent.py error filled in search head in SHC.
2016-11-11 VMW-4452 For 'Splunk Add-on for VMware' app getting error on Scheduler while adding DCN.
Last modified on 12 September, 2017
Known issues in the Splunk App for VMWare   Credits

This documentation applies to the following versions of Splunk® App for VMware (Legacy): 3.3.2


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