This documentation does not apply to the most recent version of Splunk® App for NetApp Data ONTAP (Legacy).
For documentation on the most recent version, go to the latest release.
Download topic as PDF
Fixed issues for Splunk App for NetApp Data ONTAP
Publication date | Defect number | Description |
---|---|---|
2016-10-12 | NETAPP-730 | NetApp App consuming all RAM on Indexer. |
2016-07-13 | NETAPP-621 | ONTAP Collection Configuration failed with [SSL: UNSUPPORTED_PROTOCOL]. |
2016-07-08 | NETAPP-620 | NetAppPerformance.Disk_Performance data model acceleration memory leak. |
2016-06-17 | NETAPP-618 | Broken pipe Error while accessing /services/hydra/hydra_gatekeeper/hydra_gateway in data collector node. |
2016-06-09 | NETAPP-617 | Issue: fscfs5-1a categorized as 7-mode although it’s part of the C-mode cluster |
2016-04-04 | NETAPP-613 | Netapp app does not extract "avg_latency_average" Volumes with highest latency over the past 4 hours (ms) dashboard and other dashboards are empty. |
2016-01-20 | NETAPP-608 | Credential Configuration for ONTAP displays VMWare credentials as well. |
2015-12-29 | NETAPP-604 | Ontap setup failing to reach the indexers (indexer cluster on splunkcloud) |
Last modified on 16 December, 2016
PREVIOUS Known issues for the Splunk App for NetApp Data ONTAP |
NEXT Credits |
This documentation applies to the following versions of Splunk® App for NetApp Data ONTAP (Legacy): 2.1.5
Feedback submitted, thanks!