Splunk® Supported Add-ons

Splunk Add-on for Unix and Linux

Acrobat logo Download manual as PDF


Acrobat logo Download topic as PDF

Release notes for the Splunk Add-on for Unix and Linux

Version 8.4.0 of the Splunk Add-on for Unix and Linux was released on December 07, 2021.

Compatibility

Version 8.4.0 of the Splunk Add-on for Unix and Linux is compatible with the following software, CIM versions, and platforms:

Splunk platform versions 8.1.x, 8.2.x
CIM 4.20.2
Supported OS for data collection All supported Unix operating systems. See Unix operating systems.
Vendor products All supported Unix operating systems. See Unix operating systems.

See the Scripted input reference for the Splunk Add-on for Unix and Linux page in the Reference chapter of this manual to learn more about scripted inputs and their operating system compatibility.

The field alias functionality is compatible with the current version of this add-on. The current version of this add-on does not support older field alias configurations.

For more information about the field alias configuration change, refer to the Splunk Enterprise Release Notes.

New features

Version 8.4.0 of the Splunk Add-on for Unix and Linux has the following new features:

  • Support for the latest vendor products of Nix (RHEL 8.4, Ubuntu 21.04, FreeBSD 13, and macOS 11.6)
  • Support for INode fields of all the OSs in the 'df' and 'df_metric' scripts' output
  • Support for the latest CIM version (4.20.2)
  • Added 'user_name' and 'src_user_name' fields to the 'linux_secure' and 'linux_audit' sourcetypes
  • Reinstated the 'process' tag for the 'top' and 'ps' eventtypes

Bug fixes

  • Fixed the normalisation issue for the 'pctCPU' and 'pctMEM' fields when value is either <0 or >100 in output of 'ps' and 'ps_metric' scripts.
  • Fixed the issue in 'iostat' and 'iostat_metric' scripts to support the latest version of the sysstat package.
  • Fixed the field extraction where the value of the 'user' was truncated when it contained special characters for the 'aix_secure', 'osx_secure', linux_secure', and 'syslog' sourcetypes.
  • Fixed the 'df' and 'df_metric' scripts for the incorrect data when mount point has a space character for Linux kernel OSs.
  • Fixed the 'rlog' script to remove the unwanted error in the splunkd logs when no new data is available.
  • Fixed the 'interfaces' and 'interfaces_metric' scripts to remove the warning of awk regular expression syntax.

Fixed issues

Version 8.4.0 of the Splunk Add-on for Unix and Linux has the following known issues. If no issues appear here, no issues have yet been reported:

Known issues

Version 8.4.0 of the Splunk Add-on for Unix and Linux has the following known issues. If no issues appear here, no issues have yet been reported:


Date filed Issue number Description
2021-01-20 ADDON-33139 Input netstat.sh and openPorts.sh gives error in splunkd.log when add-on is installed on macOS v10.15.7
2020-06-18 ADDON-27321 nfsiostat.sh fails with ImportError: This package should not be accessible on Python 3
2020-04-24 ADDON-26293 Field values gets broke when values has space for 'lsof' and 'userswithloginprivs' source types
2020-04-24 ADDON-26292 Additional error of broken pipe is getting logged under splunkd.log along with correct data for cpu.sh on Solaris OS
2020-04-20 ADDON-26131, ADDON-33138 Input protocol.sh gives error in splunkd.log when add-on is installed on macOS

Third-party software attributions

The Splunk Add-on for Unix and Linux does not use third-party software or libraries.

Last modified on 09 December, 2021
PREVIOUS
Source types for the Splunk Add-on for Unix and Linux
  NEXT
Release history for the Splunk Add-on for Unix and Linux

This documentation applies to the following versions of Splunk® Supported Add-ons: released


Was this documentation topic helpful?

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