Abstract: Storage array health scores based on alerts are auto-corrected by using alert validation and alert matching to identify missed, stale, and redundant alerts. In response to restoration of an event daemon or reboot of a storage management server, each alert associated with each storage array is validated to determine whether current state of storage array hardware or a logical object differs from the state indicated in the alert. Alerts that differ from current state are updated or invalidated and the health score is recalculated. Responsive to receipt of a new alert, existing alerts associated with the same storage array hardware or logical object are identified and Jaro-Winkler distance between the identified alerts and the new alert is calculated. Any existing alert for which the Jaro-Winkler distance relative to the new alert is greater than or equal to 0.9 is deleted and the health score is recalculated.

Abstract: Customized updates are generated for instances of storage management software running on storage management servers in different storage systems. The filenames of class files used by each instance of the storage management software are stored in respective databases associated with those storage management software instances. Thread dumps are created and searched for class files of the storage management software to create a baseline. The baseline is updated by comparing class files used in response to UI actions and REST API calls and storing names of class files that are not already in the database. To update an instance of the storage management software, the class files of a general update are compared with the filenames in the database associated with the instance and non-matching files are omitted from the customized update foe that instance.

Abstract: Storage objects are mapped to host applications in a storage domain. Each of the storage objects is analyzed to determine importance in terms of predetermined criteria such as quality of service of the storage object, replication level of the storage object, size of the storage object, input-output loading of the storage object, and input-output loading of a host application that uses the storage object. Storage objects that satisfy predetermined importance characteristics are automatically tagged with the name of the host application that uses the storage object. The storage objects may also be tagged with the names of data structures that satisfy predetermined importance characteristics. Storage groups, masking views, and volume devices may also be tagged.

Abstract: One or more aspects of the present disclosure relate to a storage health status. In embodiments, one or more events corresponding to a storage array can be received. Each event can include an alert. A type of each event can also be identified. For each event having a qualifying type, at least one prior event made obsolete by each received event can be cleared.

Abstract: Aspects of the present disclosure relate to controlling resource consumption of a server and storage array. In embodiments, a request can be received by a server that is communicatively coupled to a storage array. Further, the services required to process the request can be identified. Additionally, services' activation can be controlled based on a mapping of request-related actions and initiated services.

Abstract: A request manager analyzes API calls from a client to a host application for state and performance information. If current utilization of host application processing or memory footprint resources exceed predetermined levels, then the incoming API call is not forwarded to the application. If current utilization of the host application processing and memory resources do not exceed the predetermined levels, then the request manager quantifies the processing or memory resources required to report the requested information and determines whether projected utilization of the host application processing or memory resources inclusive of the resources required to report the requested information exceed predetermined levels. If the predetermined levels are not exceeded, then the request manager forwards the API call to the application for processing.

Abstract: One or more aspects of the present disclosure relate to a storage health status. In embodiments, one or more events corresponding to a storage array can be received. Each event can include an alert. A type of each event can also be identified. For each event having a qualifying type, at least one prior event made obsolete by each received event can be cleared.

Abstract: A request manager analyzes API calls from a client to a host application for state and performance information. If current utilization of host application processing or memory footprint resources exceed predetermined levels, then the incoming API call is not forwarded to the application. If current utilization of the host application processing and memory resources do not exceed the predetermined levels, then the request manager quantifies the processing or memory resources required to report the requested information and determines whether projected utilization of the host application processing or memory resources inclusive of the resources required to report the requested information exceed predetermined levels. If the predetermined levels are not exceeded, then the request manager forwards the API call to the application for processing. The request manager may implement a limited number of retries if the predetermined levels are exceeded.

Abstract: Techniques for identifying I/O workload patterns may include monitoring key performance indicators (KPIs) for a monitoring period; and at the end of the monitoring period, performing processing including: determining whether there have been a specified number of occurrences of a predefined event with respect to a data portion of the application, wherein the predefined event is a violation of an application KPI for the application and also a violation of at least one of a plurality of data storage KPIs for the data portion of the application; and responsive to determining that there have been the specified number of the occurrences of the predefined event with respect to the first data portion of the application, recording a pattern of I/O workload for the data portion in accordance with the occurrences of the predefined event. Hints, such as affecting data movement and/or compression, may be generated based on detected patterns.