Storage device health status controller
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.
1. An apparatus comprising at least one processor configured to:
receive one or more events corresponding to a storage array, wherein each event includes an alert;
identify a type of each event, wherein identifying each event type includes:
parsing metadata from each event,
generating a unique identifier based on the metadata, and
appending the unique identifier to its related event;
for each event having a qualifying type, clearing at least one prior event made obsolete by each received event, wherein the at least one prior event and its corresponding qualifying type event correspond to a matching event type; and
wherein clearing the at least one prior event includes:
determining a probability that the type of each event impacts an alert extracted from a previously received event, and
processing each event through a thread based on each event's characteristics identified by the event's metadata and each event's respective probability.
2. The apparatus of claim 1 further configured to:
communicatively couple to one or more daemons of the storage array, wherein each daemon is configured to monitor a component of the storage array and transmit one or more logs of events corresponding to the component.
3. The apparatus of claim 2 , wherein each daemon generates characteristic metadata corresponding to each event.
4. The apparatus of claim 1 further configured to:
identify a component related to each event; and
extract event content from each event.
5. The apparatus of claim 4 further configured to determine if the component corresponds to an item of interest, wherein the item of interest corresponds to a storage device component capable of impacting a health metric of the storage device.
6. The apparatus of clam 5 further configured to determine if the event content relates to a status change of the item of interest.
7. The apparatus of claim 6 further configured to pass those events having a component related to an item of interest and content related to a status change of the item of interest to an auto-clearing inspection queue.
8. The apparatus of claim 7 further configured to generate a key for each item of interest and store the key in the auto-clearing queue.
9. The apparatus of claim 8 further configured to:
obtain current alerts associated with each key;
for each key, determine if a previous alert relates to an obtained current alert; and
clear the previous alert if the obtained current alert renders the previous alert obsolete.
10. A method comprising:
receiving one or more events corresponding to a storage array, wherein each event includes an alert;
identifying a type of each event, wherein identifying each event type includes:
parsing metadata from each event,
generating a unique identifier based on the metadata, and
appending the unique identifier to its related event;
for each event having a qualifying type, clearing at least one prior event made obsolete by each received event,
wherein the at least one prior event and its corresponding qualifying type event correspond to a matching event type; and
wherein clearing the at least one prior event includes:
determining a probability that the type of each event impacts an alert extracted from a previously received event, and
processing each event through a thread based on each event's characteristics identified by the event's metadata and each event's respective probability.
11. The method of claim 10 further comprising:
receiving information from one or more daemons of the storage array, wherein each daemon monitors a component of the storage array and transmit one or more logs of events corresponding to the component.
12. The method of claim 11 further comprising generating characteristic metadata corresponding to each event.
13. The method of claim 10 further comprising:
identifying a component related to each event; and
extracting event content from each event.
14. The method of claim 13 further comprising determining if the component corresponds to an item of interest, wherein the item of interest corresponds to a storage device component capable of impacting a health metric of the storage device.
15. The method of clam 16 further comprising determining if the event content relates to a status change of the item of interest.
16. The method of claim 15 further comprising passing those events having a component related to an item of interest and content related to a status change of the item of interest to an auto-clearing inspection queue.
17. The method of claim 16 further comprising generating a key for each item of interest and storing the key in the auto-clearing queue.
18. The method of claim 17 further comprising:
obtaining current alerts associated with each key;
for each key, determining if a previous alert relates to an obtained current alert; and
clearing the previous alert if the obtained current alert renders the previous alert obsolete.