Dell Products Inc.

Emc IP Holding Company LLC

David P Moloney

Eileen Kelleher

Francisco Jaen

Lisa O'Mahony

Robert Fitzgerald

Amnon Naamad

Ron Arnan

Fatemeh Azmandian

Finbarr O'Riordan

Colm O'Leary

One or more aspects of the present disclosure relate to relate to analyzing and mitigation storage array latency. In embodiments, an input/output (IO) workload is received by a storage array. Additionally, a latency corresponding to processing one or more IO requests of the IO workload is determined. For example, a factor corresponding to a significant portion of the latency is identified. Further, a remediation action is performed based on the factor identified.

Storage array latency analysis

A cause analysis and remediation engine (CARE) can perform an analysis of inputs characterizing aspects of the system at the time an alert is generated in order to determine causes and remediation actions for the alert. The CARE can automatically detect and analyze inputs including configuration information, compliance information, and workload and performance information to determine one or more expected causes of the alert and one or more corresponding remediations that can be taken. The CARE can include a rules engine and a remediation service. The rules engine can include one or more trained models, such as trained machine learning models, each using rules to recognize inputs denoting a particular expected cause of the alert. The models can be decision trees trained using supervised learning. The remediation service can map one or more expected causes determined by the rules engine to the one or more corresponding remediations.

Analysis and remediation of alerts

Techniques for rendering a user interface may include: receiving a view area height and width, a first integer denoting a count of objects to be displayed, a minimum row height, and a minimum object width; determining a maximum allowed number of columns in accordance with the view area width and minimum object width; determining a current number of rows in accordance with the view area height, a current number of columns, the minimum row height, and the first integer; determining whether the current number of rows and columns denote an optimized layout of the objects, wherein the optimized layout is in accordance with a plurality of conditions; and responsive to determining the current number of rows and columns denote an optimized layout, rendering the plurality of objects in a view area in accordance with the current number of rows and columns.

Techniques for user interface layouts

Techniques for specifying information displayed in a graphical user interface may include: receiving a runbook definition that is a template including a primary object category, a first object category related to the primary object category, a first chart definition of metrics about the primary object category, and a second chart definition of metrics about the first object category; loading the runbook definition; applying the runbook definition to a first primary object that is an instance of the primary object category, wherein the first primary object has a first related object and the first related object is an instance of the first object category; and updating the graphical user interface to display a first chart having the first chart definition for the first primary object and to display a second chart having the second chart definition for the first related object.

Dynamic dashboard of user interface displaying primary object and related objects

A storage system management application receives reports describing operation of a storage system from a performance monitoring system, and compares the storage system operating metrics against a set of respective thresholds. If the metrics breach one or more thresholds, the seasonality boundaries for the respective metric are calculated, and an alert is only generated if the storage system operating metric is both outside the performance threshold and outside of the calculated seasonality boundaries. By determining the seasonality boundaries and using the seasonality boundaries to determine when to generate alerts, it is possible to reduce the number of alerts generated. By including the seasonality values in the alerts, the deviation from normal seasonably operating conditions can be determined from the alert, thus enabling a person who receives the alert to determine the magnitude of deviation of the storage system operation from seasonably adjusted normal operation.

Smarter performance alerting mechanism combining thresholds and historical seasonality

For each storage array in a storage system, a single value score indicative of the overall health of the respective storage array is calculated. Storage array health score may be tracked over time and used to identify storage arrays in need of maintenance. The storage array health score may be calculated as a composite of four component scores: physical component health, logical component health, Service Level Objective compliance and Best Practice Configuration Compliance. The physical component and logical component scores may be based on multiple different category health scores, and each category health score may be based on multiple instance health scores. Health scores may be used to identify remedial actions and predict health score increase as a result of remedial actions.

Growing community of inventors

Cork, Ireland

David P Moloney