Splunk® App for Infrastructure (Legacy)

Release Notes for Splunk App for Infrastructure

This documentation does not apply to the most recent version of Splunk® App for Infrastructure (Legacy). For documentation on the most recent version, go to the latest release.

Fixed issues for Splunk App for Infrastructure

The following issues are fixed in the Splunk App for Infrastructure version 2.0.0.


Date resolved Issue number Description
2019-10-03 SII-5486 Email settings link from alert modal is wrong, VictorOps settings link from alert modal is missing
2019-10-02 SII-4570 The splunkd messages service fails to send error messages when the splunkd port is not 8089.
2019-10-02 SII-5698 Memory tabs shows "Free %" which is actually "Used %" not "Free %" for Windows client
2019-09-25 SII-2924 The Entity Overview does not properly display metrics values.
2019-09-18 SII-5437 There's a conflict with transforms in the Splunk Add-on for Infrastructure and the Splunk Add-on for Microsoft Windows.
2019-09-17 SII-5411 The em_metrics sourcetype is not visible in Splunk Cloud.
2019-08-20 SII-5022 Splunk Connect for Kubernetes stops collecting the kube:objects:events:watch sourcetype.
2019-07-31 SII-4845 Container logs are not being associated with pods.
2019-07-11 SII-4876 On CentOS systems, the easy install script does not update the universal forwarder.
Last modified on 14 November, 2019
What's new in Splunk App for Infrastructure   Known issues for Splunk App for Infrastructure

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


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