ONTAP Collector failed alerts in DII due to intermittent Read time out for ZAPI calls
Applies to
- Data Infrastructure Insights (DII)
- ONTAP data collectors via ZAPI
Issue
- DII triggers intermittent collector failed alerts for various ONTAP data collectors
- Frequency of the alerts are one or more a day and randomly for all/most ONTAP data collectors
- Acqusition is done via ZAPI
acq.log:<Cluster> [Error connecting] - Failed to execute request: Read timed out: <specific_ZAPI_Call> ||| ([Device name https://<Cluster>:443]: Failed to execute request: Read timed out: <specific_ZAPI_Call>|||)com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException: Failed to execute request: Read timed out: <specific_ZAPI_Call>|||at com.onaro.sanscreen.acquisition.framework.datasource.DataSourceErrorException.createWithoutEnhanced(DataSourceErrorException.java:81) ~[au.jar:1.821.0]at com.onaro.sanscreen.acquisition.util.stream.http.HttpClient.newBadResponseException(HttpClient.java:667) ~[netapp_ontap.jar13506090608744815337.jar:?]......Caused by: java.net.SocketTimeoutException: Read timed out
