Techniques for utilizing disruptions to enterprise systems

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.

1 . An apparatus, comprising:
 a processor; and   memory comprising instructions that when executed by the processor cause the processor to:
 identify a configuration of an enterprise system, the enterprise system comprising a plurality of hardware components and a plurality of software components, wherein at least a portion of the plurality of hardware components implement the plurality of software components; 
 determine one or more targets in the enterprise system to disrupt, the one or more targets comprising at least one of a hardware component of the plurality of hardware components or a software component of the plurality of software components; 
 identify one or more disruptions to apply to each of the one or more targets, wherein each of the one or more disruptions affect operation of at least one of the one or more targets in the enterprise system; 
 determine one or more conditions for each of the one or more disruptions to apply to each of the one or more targets, the one or more conditions comprising a scope for the one or more disruptions, wherein the scope includes a threshold number of affected hardware components and affected software components in the enterprise system, wherein the threshold number comprises a plurality; 
 analyze at least one of the one or more targets, the one or more disruptions, and the one or more conditions to determine one or more timings for the one or more disruptions; 
 generate a disruption scheme for the enterprise system based on the one or more targets, the one or more disruptions, the one or more conditions, and the one or more timings, the disruption scheme including the one or more disruptions; 
 implement the disruption scheme on the enterprise system to test resiliency of the enterprise system; 
 monitor a number of affected hardware components and software components in the enterprise system during implementation of the disruption scheme; and 
 reverse implementation of the disruption scheme when the number of affected components in the enterprise system exceeds the threshold number of affected hardware components and software components during implementation of the disruption scheme. 
   
     
     
         2 . The apparatus of  claim 1 , at least one of the one or more timings for the one or more disruptions comprising a disruption window to minimize impact on user experience associated with the enterprise system. 
     
     
         3 . The apparatus of  claim 1 , at least one of the one or more timings for the one or more disruptions comprising a disruption window to maximize impact of the disruption scheme on user experience associated with the enterprise system. 
     
     
         4 . The apparatus of  claim 1 , the memory comprising instructions that when executed by the processor cause the processor to:
 monitor the one or more disruptions and one or more responses to the one or more disruptions; and   create at least one disruption event in a library based on monitoring the one or more disruptions and the one or more responses to the one or more disruptions.   
     
     
         5 . The apparatus of  claim 4 , wherein each of the at least one disruption event created in the library comprise two or more of a system state timeline, a response timeline, and a configuration timeline. 
     
     
         6 . The apparatus of  claim 1 , the memory comprising instructions that when executed by the processor cause the processor to determine at least one of the one or more targets in the enterprise system to disrupt, the one or more disruptions to affect operation of at least one of the one or more targets, and the one or more conditions based on user input. 
     
     
         7 . The apparatus of  claim 1 , the one or more conditions comprising a scope for the one or more disruptions, wherein the scope of the one or more disruptions comprises a threshold amount of or elapsed time with affected hardware components and affected software components in the enterprise system. 
     
     
         8 . The apparatus of  claim 7 , the memory comprising instructions that when executed by the processor cause the processor to return the enterprise system to a previous configuration when the scope of the one or more disruptions is exceeded. 
     
     
         9 . 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:
 determine one or more targets in an enterprise system to disrupt, the one or more targets comprising at least one of a hardware component of a plurality of hardware components in the enterprise system and a software component of a plurality of software components in the enterprise system, wherein at least a portion of the plurality of hardware components implement the plurality of software components;   identify one or more disruptions to apply to each of the one or more targets, wherein each of the one or more disruptions affect operation of at least one of the one or more targets in the enterprise system;   determine one or more conditions for each of the one or more disruptions to apply to each of the one or more targets, the one or more conditions comprising a scope for the one or more disruptions, wherein the scope includes a threshold number of affected hardware components and affected software components in the enterprise system, wherein the threshold number comprises a plurality;   analyze at least one of the one or more targets, the one or more disruptions, and the one or more conditions to determine one or more timings for the one or more disruptions;   create a disruption scheme for the enterprise system based on the one or more targets, the one or more disruptions, the one or more conditions, and the one or more timings, the disruption scheme including the one or more disruptions;   implement the disruption scheme on the enterprise system to test resiliency of the enterprise system;   monitor the one or more disruptions, one or more responses to the one or more disruptions, and a number of affected hardware components and software components in the enterprise system during implementation of the disruption scheme; and   reverse implementation of the disruption scheme when the number of affected components in the enterprise system exceeds the threshold number of affected hardware components and software components during implementation of the disruption scheme.   create at least one disruption event in a library based on monitoring the one or more disruptions and the one or more responses to the one or more disruptions.   
     
     
         10 . The at least one non-transitory computer-readable medium of  claim 9 , at least one of the one or more timings for the one or more disruptions comprising a disruption window to minimize impact on user experience associated with the enterprise system. 
     
     
         11 . The at least one non-transitory computer-readable medium of  claim 9 , at least one of the one or more timings for the one or more disruptions comprising a disruption window to maximize impact of the disruption scheme on the enterprise system. 
     
     
         12 . The at least one non-transitory computer-readable medium of  claim 9 , wherein each of the at least one disruption event created in the library comprise two or more of a system state timeline, a response timeline, and a configuration timeline. 
     
     
         13 . The at least one non-transitory computer-readable medium of  claim 9 , comprising instructions that, in response to being executed by the processor circuit, cause the processor circuit to determine at least one of the one or more targets in the enterprise system to disrupt, the one or more disruptions to affect operation of at least one of the one or more targets, and the one or more conditions based on user input. 
     
     
         14 . The at least one non-transitory computer-readable medium of  claim 9 , the one or more conditions comprising a scope of the one or more disruptions, wherein the scope for the one or more disruptions comprises a threshold amount of or elapsed time with affected hardware components and affected software components in the enterprise system. 
     
     
         15 . The at least one non-transitory computer-readable medium of  claim 14 , comprising instructions that, in response to being executed by the processor circuit, cause the processor circuit to interrupt the one or more disruptions when the scope of the one or more disruptions is exceeded. 
     
     
         16 . A computer-implemented method, comprising:
 determining a configuration of an enterprise system, the enterprise system comprising a plurality of hardware components and a plurality of software components, wherein at least a portion of the plurality of hardware components implement the plurality of software components;   identifying one or more targets in the enterprise system to disrupt, the one or more targets comprising at least one of a hardware component of the plurality of hardware components or a software component of the plurality of software components;   determining one or more disruptions to apply to each of the one or more targets, wherein each of the one or more disruptions affect operation of at least one of the one or more targets in the enterprise system;   identifying one or more conditions for each of the one or more disruptions to apply to each of the one or more targets, the one or more conditions comprising a scope for the one or more disruptions, wherein the scope includes a threshold number of affected hardware components and affected software components in the enterprise system, wherein the threshold number comprises a plurality;   analyzing at least one of the one or more targets, the one or more disruptions, and the one or more conditions to determine one or more timings for the one or more disruptions;   creating a disruption scheme for the enterprise system based on the one or more targets, the one or more disruptions, the one or more conditions, and the one or more timings, the disruption scheme including the one or more disruptions;   implementing the disruption scheme on the enterprise system to test resiliency of the enterprise system;   monitoring a number of affected hardware components and software components in the enterprise system during implementation of the disruption scheme; and   reversing implementation of the disruption scheme when the number of affected components in the enterprise system exceeds the threshold number of affected hardware components and software components during implementation of the disruption scheme.   
     
     
         17 . The computer-implemented method of  claim 16 , at least one of the one or more timings for the one or more disruptions comprising a disruption window to minimize impact on user experience associated with the enterprise system. 
     
     
         18 . The computer-implemented method of  claim 16 , at least one of the one or more timings for the one or more disruptions comprising a disruption window to maximize impact of the disruption scheme on the enterprise system. 
     
     
         19 . The computer-implemented method of  claim 16 , comprising:
 monitoring the one or more disruptions and one or more responses to the one or more disruptions; and   creating at least one disruption event in a library based on monitoring the one or more disruptions and the one or more responses to the one or more disruptions.   
     
     
         20 . The computer-implemented method of  claim 19 , wherein each of the at least one disruption event created in the library comprise two or more of a system state timeline, a response timeline, and a configuration timeline.