Failure impact analysis of network events

4:

• The method of claim 3, wherein identifying the third resource includes:
• generating, based on the dependencies modeled by the resource graph, a fourth event caused by the second event, wherein the fourth event is a logical event;
• and
• identifying the third resource as a resource associated with the fourth event.

7:

• The method of claim 1, further comprising:
• detecting, by the control system and before generating the second event, a fourth id event affecting the second resource, wherein the fourth event is a network event;
• and
• merging, by the control system and after generating the second event, the second event into the fourth event.

10:

• The method of claim 1, wherein generating the resource graph includes:
• receiving programming input;
• and
• generating the resource graph based on the programming input.

12:

• A system comprising:
• a network including a plurality of resources;
• and
• a controller capable of communicating with each of the plurality of resources and configured to:
• generate a resource graph that models resource and event dependencies between a plurality of resources within the resource group,
• detect a first event affecting a first resource of the plurality of resources, wherein the first event is a network event,
• identify, based on the dependencies modeled by the resource graph, a second resource that is expected to be affected by the first event, wherein to identify the second resource, the controller is further configured to:
• generate, based on the dependencies modeled by the resource graph, a second event caused by the first event, wherein the second event is a logical event, and
• identify the second resource as a resource associated with the second event,
• detect, after generating the second event, a third event affecting the second resource, wherein the third event is a network event, and
• merge the third event into the second event to avoid duplicative processing associated with the third event.

15:

• The system of claim 14, wherein to identify the third resource, the controller is further configured to:
• generate, by applying the dependencies modeled by the resource graph, a fourth event caused by the second event, wherein the fourth event is a logical event;
• and
• identify the third resource as a resource associated with the fourth event.

18:

• The system of claim 2, wherein the controller is further configured to:
• detect, before generating the second event, a third event affecting the second resource, wherein the third event is a network event;
• and
• merge, after generating the second event, the second event into the third event.

20:

• A non-transitory computer-readable storage medium comprising instructions that, when executed, configure processing circuitry of a computing system to:
• generate a resource graph that models resource and event dependencies between a plurality of resources within the resource group;
• detect a first event affecting a first resource of the plurality of resources, wherein the first event is a network event;
• identify, based on the dependencies modeled by the resource graph, a second resource that is expected to be affected by the first event, wherein to identify the second resource, the processing circuitry is further configured to:
• generate, based on the dependencies modeled by the resource graph, a second event caused by the first event, wherein the second event is a logical event, and
• identify the second resource as a resource associated with the second event,
• detect, after generating the second event, a third event affecting the second resource, wherein the third event is a network event;
• and
• merge the third event into the second event to avoid duplicative processing associated with the third event.