Risks, Limitations, and Assumptions

• The application handles Critical and Recovery failure notifications in these cases when you enable App Failure Notifications in the configuration:
  • Connectivity exceptions
  • Authentication exceptions
• The application does not send duplicate or repeat failure alert notifications until the existing critical alert is resolved.
• Use metrics to monitor resources and generate alerts when threshold values are exceeded.
• The application cannot control monitoring pause and resume actions based on these alerts.
• SolidFire event and alert polling starts only if you enable Event Polling in the configuration.
• Alert Severity Filter configuration property values are: warning, critical, and error.
• OpsRamp provides sample mappings to map SolidFire Severity to OpsRamp Severities in the Event/Alert Severity Mapping configuration field. You can modify these mappings at any time from the SDK application configuration page. Possible OpsRamp Severities are: Critical, Warning, Ok, and Info.
• Activity logs and applied time are not supported.
• The application is not compatible with Cluster Gateway.
• NetApp SolidFire does not provide resource names for drive resources. Drive resource names are formatted as a combination of driveId, nodeId, and chassis-slot. Example: 1.1.1 (driveId.nodeId.chassis-slot).
• When no resource filter conditions are met, all resources are discovered.