Stackable system event clearinghouse for cloud computing
An event clearinghouse engine is used with a data storage system to modify event disposition associated with components. A separate component disposition table is provided for each component. The component disposition table specifies different sets of disposition modifications for different types of events as indicated by event ID. A global disposition rule mapping table includes disposition modifications which are applied to all events. Per-vendor and per-tenant tables may be used to specify disposition modifications for particular vendors and tenants. Mode-specific tables such as a rescue/recovery mode table may be used to specify disposition modifications when the storage system is in a particular mode. The tables may be implemented in stages, including parallel and serial application.
1. A method comprising:
collecting events associated with a plurality of components comprising at least one of software modules and hardware subsystems, the events comprising at least one of component operational status changes, component errors, component system configuration changes and component statistics updates;
for at least one of the events collected from one of the components, modifying disposition of the event as indicated by a component disposition indicator, including selecting a set of multiple recipients for notification of the event, where the multiple recipients are not specified by the component and a separate component disposition indicator is provided for each component of the plurality of components; and
processing each event in accordance with a modified disposition associated with that event, including sending the notification of the event to the set of recipients.
2. The method of claim 1 wherein collecting events includes utilizing at least one of: control path object management modules, event daemons and health monitoring components.
3. The method of claim 1 wherein the component disposition indicator includes multiple sets of disposition instructions indexed by event identifier, and including selecting one of the sets based on an event identifier associated with an event being processed.
4. The method of claim 1 wherein the component disposition indicator includes a default set of instructions for events having an identifier which does not match a specified identifier or range, and including selecting the default set based on an event identifier associated with an event being processed.
5. The method of claim 1 including, for each event, further modifying disposition of the event as indicated by a global component disposition indicator, where a single global component disposition indicator is provided for all components of the plurality of components.
6. The method of claim 5 wherein further modifying disposition of the event includes overriding disposition of the event as indicated by the component disposition indicator.
7. The method of claim 1 including further modifying disposition of the event as indicated by a service vendor indicator, where a single service vendor indicator is provided for all events associated with a specified service vendor.
8. The method of claim 1 including further modifying disposition of the event as indicated by a tenant indicator, where a single tenant indicator is provided for all events associated with a specified tenant.
9. The method of claim 1 including further modifying disposition of the event as indicated by a mode-specific indicator, where a single mode-specific indicator is provided for all events when the specified mode is active.
10. Computer program code stored in non-transitory memory comprising:
logic which collects events associated with a plurality of components comprising at least one of software modules and hardware subsystems, the events comprising at least one of component operational status changes, component errors, component system configuration changes and component statistics updates;
for at least one of the events collected from one of the components, logic which modifies disposition of the event as indicated by a component disposition indicator, including selecting a set of multiple recipients for notification of the event, where the multiple recipients are not specified by the component and a separate component disposition indicator is provided for each component of the plurality of components; and
logic which processes each event in accordance with a modified disposition associated with that event, including sending the notification of the event to the set of recipients.
11. The program code of claim 10 wherein the logic which collects events utilizes at least one of: control path object management modules, event daemons and health monitoring components.
12. The program code of claim 10 wherein the component disposition indicator includes multiple sets of disposition instructions indexed by event identifier, and including logic which selects one of the sets based on an event identifier associated with an event being processed.
13. The program code of claim 10 wherein the component disposition indicator includes a default set of instructions for events having an identifier which does not match a specified identifier or range, and including logic which selects the default set based on an event identifier associated with an event being processed.
14. The program code of claim 10 including, for each event, logic which further modifies disposition of the event as indicated by a global component disposition indicator, where a single global component disposition indicator is provided for all components of the plurality of components.
15. The program code of claim 14 wherein the logic which further modifies disposition of the event overrides disposition of the event as indicated by the component disposition indicator.
16. The program code of claim 10 including logic which further modifies disposition of the event as indicated by a service vendor indicator, where a single service vendor indicator is provided for all events associated with a specified service vendor.
17. The program code of claim 10 including logic which further modifies disposition of the event as indicated by a tenant indicator, where a single tenant indicator is provided for all events associated with a specified tenant.
18. The program code of claim 10 including logic which further modifies disposition of the event as indicated by a mode-specific indicator, where a single mode-specific indicator is provided for all events when the specified mode is active.
19. Apparatus comprising:
a data storage system including data storage resources; and
at least one storage management device which:
collects events associated with a plurality of components comprising at least one of software modules and hardware subsystems, the events comprising at least one of component operational status changes, component errors, component system configuration changes and component statistics updates;
for at least one of the events collected from one of the components, modifies disposition of the event as indicated by a component disposition indicator, including selecting a set of multiple recipients for notification of the event, where the multiple recipients are not specified by the component and a separate component disposition indicator is provided for each component of the plurality of components; and
processes each event in accordance with a modified disposition associated with that event, including sending the notification of the event to the set of recipients.
20. The apparatus of claim 19 wherein the at least one storage management device collects events by utilizing at least one of: control path object management modules, event daemons and health monitoring components.
21. The apparatus of claim 19 wherein the component disposition indicator includes multiple sets of disposition instructions indexed by event identifier, and wherein the at least one storage management device selects one of the sets based on an event identifier associated with an event being processed.
22. The apparatus of claim 19 wherein the component disposition indicator includes a default set of instructions for events having an identifier which does not match a specified identifier or range, and wherein the at least one storage management device selects the default set based on an event identifier associated with an event being processed.
23. The apparatus of claim 19 wherein, for each event, the at least one storage management device further modifies disposition of the event as indicated by a global component disposition indicator, where a single global component disposition indicator is provided for all components of the plurality of components.
24. The apparatus of claim 23 wherein further modification of disposition of the event overrides disposition of the event as indicated by the component disposition indicator.
25. The apparatus of claim 19 wherein the at least one storage management device further modifies disposition of the event as indicated by a service vendor indicator, where a single service vendor indicator is provided for all events associated with a specified service vendor.
26. The apparatus of claim 19 wherein the at least one storage management device further modifies disposition of the event as indicated by a tenant indicator, where a single tenant indicator is provided for all events associated with a specified tenant.
27. The apparatus of claim 19 wherein the at least one storage management device further modifies disposition of the event as indicated by a mode-specific indicator, where a single mode-specific indicator is provided for all events when the specified mode is active.