Techniques for utilizing disruptions to enterprise systems

Patent metadata

Field	Value
Publication number	US-12399760-B2
Application number	US-202117501690-A
Country	US
Kind code	B2
Filing date	Oct 14, 2021
Priority date	Dec 30, 2019
Publication date	Aug 26, 2025
Grant date	Aug 26, 2025

Abstract

Various embodiments are generally directed to techniques for utilizing disruptions to enterprise systems, such as to test and/or improve the ability of the enterprise system to recover from system failures, for instance. In many embodiments, an enterprise system may include two or more networked components, such as hardware components and software components. Some embodiments are particularly directed to generating a disruption scheme for an enterprise system based on analysis of one or more aspects of the enterprise system. For example, embodiments may include one or more of planning, scheduling, creating, timing, implementing, administering, and/or strengthening against a disruption to an enterprise system in a controlled and monitored manner. In many embodiments, administration of a disruption scheme may be monitored, recorded, and/or analyzed. In many such embodiments, a library of disruption events may be generated based on monitoring, recording, and/or analyzing implementation of the disruption scheme.

First claim

The invention claimed is:

1. An apparatus, comprising:
a processor; and
memory comprising instructions that when executed by the processor cause the processor to:
implement a disruption scheme to an initial configuration of an enterprise system to test the enterprise system, the disruption scheme comprising one or more disruptions and the enterprise system comprising a plurality of components;
monitor the one or more disruptions and one or more responsive actions taken in response to the one or more disruptions;
determine at least one remedying action of the one or more responsive actions that remedied at least one of the one or more disruptions;
monitor for a threshold condition during the disruption scheme, the threshold condition comprising at least one of:
a number of affected components of the plurality of components affected by the disruption scheme exceeds a components threshold, or
an elapsed time with affected components exceeds a time threshold;

return the enterprise system to the initial configuration responsive to detection of the threshold condition; and
create at least one disruption event in a library based on monitoring the one or more disruptions and the one or more responsive actions taken in response to the one or more disruptions, the at least one disruption event comprising a system state timeline, a response timeline, a configuration timeline, and the at least one remedying action, wherein the response timeline comprises a first mapping, over time, of the one or more responsive actions, including failover operations or auxiliary resources being deployed, taken in response to the one or more disruptions, and wherein the configuration timeline includes a second mapping of changes over time of data sources and respective destinations for one or more components in in the enterprise system;
wherein the first mapping includes one or more nodes and one or more edges, each node representing a software or hardware component of the enterprise system and each edge representing connections, including data paths, between the software or hardware components.

2. The apparatus of claim 1 , wherein the one or more responsive actions include failover operations; and
wherein the threshold condition comprises the number of affected components of the plurality of components affected by the disruption scheme exceeds a components threshold.

3. The apparatus of claim 1 , wherein the one or more responsive actions include deployment of auxiliary resources.

4. The apparatus of claim 1 , wherein the system state timeline comprises a third mapping, over time, of an operational state over time of at least one component in the enterprise system.

5. The apparatus of claim 4 , wherein the operational state includes one or more of a health status, a capacity, a bandwidth, a load, and a traffic flow.

6. The apparatus of claim 1 , wherein the configuration timeline further comprises:
a fourth mapping, over time, of interdependencies between two or more components in the enterprise system; and
settings of the one or more components and how the settings change over time.

7. At least one non-transitory computer-readable medium comprising a set of instructions that, in response to being executed by a processor circuit, cause the processor circuit to:
implement a disruption scheme to an initial configuration of an enterprise system to test the enterprise system, the disruption scheme comprising one or more disruptions and the enterprise system comprising a plurality of components;
monitor the one or more disruptions and one or more responsive actions taken in response to the one or more disruptions;
determine at least one remedying action of the one or more responsive actions that remedied at least one of the one or more disruptions;
monitor for a threshold condition during the disruption scheme, the threshold condition comprising at least one of:
a number of affected components of the plurality of components affected by the disruption scheme exceeds a components threshold, or
an elapsed time with affected components exceeds a time threshold;

return the enterprise system to the initial configuration responsive to detection of the threshold condition; and
create at least one disruption event in a library based on monitoring the one or more disruptions and the one or more responsive actions taken in response to the one or more disruptions, the at least one disruption event comprising a system state timeline, a response timeline, a configuration timeline, and the at least one remedying action, wherein the response timeline comprises a first mapping, over time, of the one or more responsive actions, including failover operations or auxiliary resources being deployed, taken in response to the one or more disruptions, and wherein the configuration timeline includes a second mapping of changes over time of data sources and respective destinations for one or more components in in the enterprise system;
wherein the first mapping includes one or more nodes and one or more edges, each node representing a software or hardware component of the enterprise system and each edge representing connections, including data paths, between the software or hardware components.

8. The at least one non-transitory computer-readable medium of claim 7 , wherein the one or more responsive actions include failover operations; and
wherein the threshold condition comprises the number of affected components of the plurality of components affected by the disruption scheme exceeds a components threshold.

9. The at least one non-transitory computer-readable medium of claim 7 , wherein the one or more responsive actions include deployment of auxiliary resources.

10. The at least one non-transitory computer-readable medium of claim 7 , wherein the system state timeline comprises a third mapping, over time, of an operational state over time of at least one component in the enterprise system.

11. The at least one non-transitory computer-readable medium of claim 10 , wherein the operational state includes one or more of a health status, a capacity, a bandwidth, a load, and a traffic flow.

12. The at least one non-transitory computer-readable medium of claim 7 , wherein the configuration timeline comprises:
a fourth mapping, over time, of interdependencies between two or more components in the enterprise system; and
settings of the one or more components and how the settings change over time.

13. A computer-implemented method, comprising:
implementing a disruption scheme to an initial configuration of an enterprise system to test the enterprise system, the disruption scheme comprising one or more disruptions and the enterprise system comprising a plurality of components;
monitoring the one or more disruptions and one or more responsive actions taken in response to the one or more disruptions;
determining at least one remedying action of the one or more responsive actions that remedied at least one of the one or more disruptions;
monitoring for a threshold condition during the disruption scheme, the threshold condition comprising at least one of:
a number of affected components of the plurality of components affected by the disruption scheme exceeds a components threshold, or
an elapsed time with affected components exceeds a time threshold;

returning the enterprise system to the initial configuration responsive to detection of the threshold condition; and
creating at least one disruption event in a library based on monitoring the one or more disruptions and the one or more responsive actions taken in response to the one or more disruptions, the at least one disruption event

Assignees

• Capital One Services Llc

Inventors

• Barnum Eric K
• Pinos Bryan
• Helbing Lindsay

Classifications

• G06F11/3644

  by instrumenting at runtime · CPC title

• G06F3/0629

  Configuration or reconfiguration of storage systems · CPC title

• G06Q10/06395

  Quality analysis or management · CPC title

• G06F11/3684

  for test design, e.g. generating new test cases · CPC title

• G06F11/3688

  for test execution, e.g. scheduling of test suites · CPC title