Release history for Splunk Add-on for NetApp Data ONTAP

The latest version of the Splunk Add-on for NetApp Data ONTAP is version 3.1.1. See Release notes for the Splunk Add-on for NetApp Data ONTAP for the release notes of this latest version.

Version 3.1.0

Update	Description
Python 3.9 support	Updated the code to make it compatible with python 3.9 and removed legacy code related to Python 2.7 support.
Added HSTS header for Hydra communication	Added the HSTS header to prevent HTTP connection over Hydra gateway.

Version 3.0.5

Update	Description
Log Injection Vulnerability Fixes	Version 3.0.5 of Splunk Add-on for NetApp Data OnTap now has the fix of log injection vulnerabilities. This makes the Add-on more secure by fixing loggers from the ASCII Escape characters injection.

Version 3.0.3

Update	Description
Added triggers stanza for custom configuration files	To avoid unnecessary restarts of the Splunk platform, app.conf file was updated with a [triggers] stanza and a reload setting for custom configuration file.

Version 3.0.2

Update	Description
Self-service add-on installation compatibility	Splunk Add-on for NetApp Data Ontap is now compatible with self-service add-on installation in Cloud environments.
jQuery 3.5 compatibility	The Splunk Add-on for NetApp Data ONTAP now uses jQuery v3.5.0. The add-on uses jQuery v3.5 in Splunk Enterprise version 8.2 or higher. This makes the add-on more secure by fixing known cross-site scripting (XSS) related vulnerabilities as well as vulnerabilities created by object prototype pollution.
Hydra troubleshooting dashboards in the Extractions package	The Hydra troubleshooting dashboards Hydra Framework Status and Hydra Scheduler Status have been added to the TA-ONTAP-FieldExtractions package to remove the dependency of SA-Hydra from the search head. The SA-Hydra package is no longer required on the search head.
Removal of SA-VMNetAppUtils module from the add-on package	Splunk Add-on for NetApp Data ONTAP does not use any KO or modules from SA-VMNetAppUtils package. This module is no longer required and is removed from the add-on package. If you are using the module, then you can keep the module as is.

Splunk Add-on for NetApp Data ONTAP Indexes (SA-ONTAPIndex) and Splunk Add-on for NetApp Data ONTAP Extractions (TA-ONTAP-FieldExtractions) packages have been removed from the add-on package and published as independent apps with version 3.0.2 in order to support self-service installation in the cloud environment.

Version 3.0.1

In Splunk Add-on for NetApp Data ONTAP version 3.0.1, occurrences of biased terms such as master, slave, blacklist, and whitelist have been replaced with appropriate non-biased terms. The occurrences of biased terms that are Splunk platform references or present in the third-party library have not been removed.

If you are using per_panel_filter, ppf_subsearch, ppf_subsearch_dm, and per_panel_filter_lookup macros of the SA-VMNetAppUtils package in your custom dashboard or in the saved searches, then you must update the value of the filter field in the lookup file where you're using with these macros. All static variables values for ppf_lookup_type, ppf_filter have been updated from blacklist to denylist, and from whitelist to allow list.

This version of the Splunk Add-on for NetApp Data ONTAP has the following reported known issues and workarounds. If no issues appear below, no issues have yet been reported.

Date filed	Issue number	Description
2020-09-02	NETAPP-937	There's an invalid key error on Splunk 7.x because the Addon uses the Python 3 interpreter by default.
2017-03-08	NETAPP-801	Need to extract "ontap_version" field for NETAPP cluster mode having API version higher than v1.30.

Version 2.1.6

Starting in version 2.1.5 of the Splunk App for NetApp Data ONTAP, the SA-Utils package required on the search head, scheduler and DCNs has been replaced with SA-VMWNetAppUtils. For more information on upgrading from a previous version of the Splunk App for NetApp Data ONTAP, see the upgrade steps in the Splunk App for NetApp Data ONTAP manual.

NetApp changed the default behavior of the API perf-object-instance-list-info-iter and objectname "system", starting with the NETAPP API v1.30. The below returns aggregated data instead of node level data. Because of this, the below fields are not returned starting from API v1.30.

• compile_flags
• hostname
• node_name
• node_uuid
• ontap_version
• process_name
• serial_no
• system_id
• system_model

Fixed Issues

Date resolved	Issue number	Description
2017-03-09	NETAPP-796	NetApp changed the default behavior of the API "perf-object-instance-list-info-iter" and objectname "system", starting with the NETAPP API v1.30

Known Issues

Date	Issue number	Description
2017-05-03	NETAPP-821	Fields are not returned in API response starting from v1.30.

Date filed	Issue number	Description
2017-09-11	NETAPP-831	Update SA-Hydra version from 4.0.5 to 4.0.6 and SA-VMNetAppUtils version from 1.0.1 to 1.0.2
2017-03-08	NETAPP-801	Need to extract "ontap_version" field for NETAPP cluster mode having API version higher than v1.30.