New REST API Netapp check failing in AWS

Hey,

Recently moved from 2.1.0 to 2.30, I wanted to test/implement the new Netapp check with REST API instead of WebAPI.

FSX in AWS is a Netapp behind we can partially manage, while the Webapi comes with a warning at “NetApp filer connection” :

Querying class perf-object-instance-list-info-iter: Counter collection is disabled, Querying class environment-sensors-get-iter: Insufficient privileges: user ‘fsxadmin’ does not have read access to this resource.

We still have bunch of info like aggregation, CPU, diag status, lun, volumes, battery…

The new check is failing completely :

[special_netapp_ontap]: netapp_ontap.error.NetAppRestError: Caused by HTTPError('403 Client Error: Forbidden for url: https://xxxxxxxxx/api/storage/disks?fields=uid%2Cserial_number%2Cmodel%2Cvendor%2Ccontainer_type%2Cusable_size%2Cbay%2Cbytes_per_sector%2Csector_count’ not authorized for that command

Ideas :

  • Allowing in the config of the new check the possibility to select which info we want.
  • Implement the new check like the old one, raising a warning for info it couldn’t grab but still showing the rest.

Regards,

Vincent

Hi Vincent!

I’d suggest to take a look at our ideas portal and maybe submit your ideas there: https://ideas.checkmk.com/

Thanks Sara ! I was looking at that suggestion before posting here.