Risks, Limitations and Assumptions

  • The application can handle Critical/Recovery failure notifications for the below two cases when the user enables App Failure Notifications in configuration:
    • Connectivity Exception
    • Authentication Exception
  • The application will send duplicate/repeat failure alert notifications every six hours.
  • The application cannot control monitoring pause/resume actions based on the above alerts.
  • Metrics can be used to monitor Dell PowerVault resources and can generate alerts based on the threshold values.
  • The minimum supported version for the option to get the latest snapshot metric is NextGen Gateway 14.0.0.
  • Full discovery support requires gateway version 15.0.0 or above.
  • The application is not compatible with Cluster Gateway.
  • OpsRamp has provided 443 as the default Port value for processing Dell PowerVault REST APIs. Users can modify this value from the application configuration page at any point of time if required.
  • The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
  • All the credential fields in the configuration are mandatory to discover and monitor Dell PowerVault resources.
  • Alert polling is not supported for Dell PowerVault, as the alerts API (GET /api/show/alerts) does not provide the following details:
    • Time filters to fetch alerts in a specific time frame.
    • A unique field to correlate an unresolved alert and its resolved alert.
  • The application performs read-only monitoring only; no provisioning or mutating calls are performed.
  • A few metrics depend on the corresponding API call being available on the array (for example, show configuration for tier capacity and show pool-statistics for pool performance).
  • Statistics are polling-based (IOPS and bytes-per-second are point-in-time samples); push/streaming telemetry is not supported.
  • Session keys expire after inactivity and must be re-obtained.
  • Some counters are cumulative since the last reset and must be rate-converted client-side.
  • Health/status values are reported as a string plus a numeric enum; alerting should be based on the numeric value.