Related Answers
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.
Download topic as PDF
Fixed problems
3.0 Fixes
- In the Splunk App for VMware on the Proactive Monitoring > Entity Views > Cluster Detail page, when you set the time range to the last 15 minutes, the chart fails to display results for the selected time frame. (SOLNVMW-2552). The search command is using a 15min summary index instead of using raw data for selected 15min time range.
- In the Capacity planning for clusters - CPU Headroom page, when a time period of "last 24 hours" is selected to show the cpu usage of the VM over that period, the time stamps for the intervals in the chart are not displayed. (SOLNVMW-2405).
- On the Proactive Monitoring > Entity views > Cluster detail page, the cluster name in the panel title becomes "noClusterServices" when the Total Effective Processing field has a value of noClusterServices. (SOLNVMW-2388)
- "User Changes on ESX/i hosts in the last 7 days" is not affected by timerange picker on Security Overview (SOLNVMW-2310).
Last modified on 22 July, 2013
|
PREVIOUS Known issues and workarounds |
This documentation applies to the following versions of Splunk® App for VMware (Legacy): 3.0
Feedback submitted, thanks!