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

Date resolved Issue number Description
2018-08-19 VMW-4856 Getting similar information in the drilldown of both the datastores if a VM is attached to two different datastores on Virtual Machine Detail Page
2018-08-01 VMW-4731 Datastore-Detail-Dashboard are not populating
2018-07-30 VMW-4886 Dashboards throwing validation warnings when open in edit mode
2018-07-30 VMW-4895 Capacity Planning for Clusters - Memory Headroom dashboard uses static value for TotalCapacity and SafeUsage
Last modified on 17 December, 2018
Known issues in the Splunk App for VMWare   Credits

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


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