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 3.1.1

  • Licenser does not recognize license on remote license master. Also improved code to document and group licensealert fields, and simplify subclass validation making them resilient when introducing new fields.(SOLNVMW-3837)
  • VMWapp Home view contains misleading info. Home view's gauges display 0% if the number of hosts/VMs in critical state are less than 1%. This is misleading; for example, if total number of VMs is 10000, and 50 hosts are in critical range, the view still show 0% even though 0.5% are actually in critical state. (SOLNVMW-3817)
  • Incorporate 60-day trial license. The app automatically grants you a 60-day trial license upon initial download of the Splunk App for VMWare. (SOLNVMW-3785)
  • Update the documentation to produce a tighter, shorter installation guide. (SOLNVMW—3807)
  • When Installing VMware version 3.0.2 or later on the same Splunk instance as NetApp version 2.0.1, use the same version of SA-Hydra and SA-Utils on all components of the Distributed Collection Scheduler for both apps. (SOLNVMW-3770)
  • Warning messages are displayed for ta_vmware_collection_worker modular inputs. To avoid these warnings, install SA-Utils and SA-Hydra on the indexers in your environment.(SOLNVMW-3674)
  • Data collection nodes are not listed on the cluster search head. When the Splunk App for VMware is deployed in a cluster, all of the configuration tasks are performed on the master node. When the rest endpoint is called on the search head, no results are returned and the Data Collection Nodes panel in the App Install Health page (on the search head) can not populate with information about the data collection nodes. (SOLNVMW-3666)
  • JqueryUI error with JS minification Off. When running the Splunk App for VMware on Splunk version 6.x, if JS minification is turned off in Splunk Web, the Collection Configuration dashboard freezes. (SOLNVMW-3429)
  • Splunkd process is killed due to high memory usage on the indexers. (SOLNVMW-3379)
  • License warning messages are displayed for all users. The messages are intended only for admin users with license edit privileges. Please ignore the messages if you are not an admin user. (SOLNVMW-3357), (SOLNVMW-3368)
  • In certain cases inventory data gaps can be more than 4 hours. (SOLNVMW-3271)
  • The app has no control over resetting Syslog for hosts that are disconnected but once were connected to a vCenter. The host can still forward Syslog data. (SOLNVMW-3234).
Last modified on 08 October, 2014
Known issues in Splunk App for VMWare 3.1.1   Credits

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


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