Persona:
Centreon administrator

Problem to solve:
In the current NetApp Ontap REST API – volumes mode, thresholds are calculated based only on the current volume size.
For volumes with autogrow enabled, this makes percentage usage misleading since the effective limit is defined by the autosize maximum setting.

Current behavior:
The plugin retrieves size but does not consider the autosize object returned by the ONTAP REST API.
Example from a production environment (anonymized):

"autosize": { "maximum": 274877906944, "minimum": 10737418240, "grow_threshold": 85, "shrink_threshold": 50, "mode": "grow_shrink" }

Expected outcome:
Allow the plugin to use autosize.maximum as an optional reference for threshold calculation.
Users could choose between:

• Default: thresholds based on the current volume size.

• Optional: thresholds based on the autosize.maximum value.

Potential solutions:

• Extend the REST query to include autosize.maximum from /api/storage/volumes (API reference).

• Add a new option (e.g. --use-autosize-maximum or similar).

• Adjust perfdata labels to clearly distinguish between both reference types.

Benefits / Impact:

• Enables accurate monitoring of autogrow volumes.

• Prevents false alerts when volumes expand automatically.

• Aligns threshold logic with NetApp’s operational behavior, improving reliability in large environments.