Fixed issues in Splunk App for VMWare 3.1.4
Publication Date | Defect number | Description |
2015-3-13 | TAG-8961 |
License status check requires a user to refresh after several hours to maintain a valid license. The problem results from a missing ModularInput scheme in [vmware_licensecheck://<name>] log_level = <value> * log level of modular inputs from "DEBUG", "INFO", "WARN","WARNING", "ERROR" |
2015-3-13 | TAG-8924 |
The VMware license has a floating point value. This license value should be an integer. When the License check validation fails, VMware views fail to display and are routed to a License view page. |
2014-12-18 | TAG-8885 | reliability: intermittent timestamp parsing errors from ta_vmware_collection_worker.py |
2014-12-18 | TAG-8886 | reliability: intermittent errors with "could not refresh the hydra health conf for node" |
2014-12-18 | TAG-8887 | reliability: intermittent errors from Splunk_TA_vmware/bin/ta_vmware_collection_scheduler.py |
2014-12-18 | TAG-8889 | reliability: intermittent errors with "local.meta: Refused forced reload: outstanding write" |
2014-12-18 | SOLNVMW-3874 / TAG-8265 | License term reported as unlimited when pointing to a remote master with a trial license. |
Known issues in Splunk App for VMWare 3.1.4 | Credits |
This documentation applies to the following versions of Splunk® App for VMware (Legacy): 3.1.4
Feedback submitted, thanks!