The results of matrix subtraction can identify for a DevOps team sources of changes in dynamic behavior of a process or network of microservices, enabling the DevOps team to identify a microservice that should be rolled back in order to bring the process or network of microservices back to a “normal” or “well-functioning state.” In one embodiment, system 100 responds to a system error or subpar performance of one or more processes by determining a likely source of the problem. The likely source can be determined by constructor 112 generating a current matrix, either an invocation matrix corresponding to a specific process if the process is positively identified as experiencing the problem or, if the specific process is not identified, a network matrix. The prior version of the matrix can be subtracted from the newly generated current version of the matrix by analyzer 114. Matrix subtraction can be used for determining the likely source if the problem stems from a change related to the microservices. The matrix resulting from matrix subtraction will have zeros in any cells corresponding to microservices that have not been updated, not newly added, or for which interfaces have not been added or dropped. A cell or cells having a non-zero value, however, indicates such a change (or changes) having been made between generation of the current matrix and the prior matrix. A non-zero value in one or more columns corresponds to a microservice that is called by one or more other microservices, each calling microservice indicated by the row of a non-zero cell. System 100 can perform a roll back to the prior version of the called microservice in order to restore affected processes to the well-functioning state that obtained prior to the change.