Systems and methods for risk awareness using machine learning techniques
A method for training and using a machine-learning based model to reduce and troubleshoot incidents in a system may include receiving first metadata regarding a previous modification, extracting a first feature from the received first metadata, receiving second metadata regarding a previous incident, extracting a second feature from the received second metadata, training the machine-learning based model to learn an association between the previous modification and the previous incident, based on the extracted first feature and the extracted second feature, and using the machine-learning based model to determine a risk level for a proposed modification to a system.
1. A method comprising, performing by one or more processors, operations including:
automatically determining, using a trained machine-learning based model, a risk level for a proposed modification to a system, wherein the proposed modification includes a modification to code of a software component of the system,
determining whether the code is a critical code segment or a non-critical code segment, and
performing at least one of:
providing a suggested action for reducing the determined risk level for the proposed modification when the code is determined to be a non-critical code segment and the determined risk level is above a non-critical code predetermined threshold, or
blocking the proposed modification from being implemented when the code is determined to be a critical code segment and the determined risk level is above a critical code predetermined threshold.
2. A method for determining a risk level for a proposed modification to a system, the method comprising, performing by one or more processors, operations including:
receiving metadata regarding the proposed modification to the system;
extracting a feature from the received metadata, the extracted feature corresponding to a feature of a trained machine-learning based model for determining the risk level for the proposed modification based on a learned association between the extracted feature and an incident occurring in the system; and
automatically determining the risk level for the proposed modification based on the extracted feature, by using the trained machine-learning based model that was trained based on a first feature extracted from metadata regarding a previous modification to the system and a second feature extracted from metadata regarding a previous incident related to the previous modification occurring in the system, based on the learned association between the extracted feature and the incident occurring in the system,
wherein the proposed modification includes a modification to code of a software component of the system, and
wherein the operations further include:
determining whether the code is a critical code segment or a non-critical code segment, and
performing at least one of:
providing a suggested action for reducing the determined risk level for the proposed modification when the code is determined to be a non-critical code segment and the determined risk level is above a non-critical code predetermined threshold, or
blocking the proposed modification from being implemented when the code is determined to be a critical code segment and the determined risk level is above a critical code predetermined threshold.
3. The method of claim 2 , wherein the operations further include:
providing an alert identifying the determined risk level for the proposed modification to the system.
4. The method of claim 3 , wherein the providing the alert further includes:
providing a suggested action for reducing the determined risk level for the proposed modification to the system.
5. The method of claim 3 , wherein the providing the alert further includes:
blocking the proposed modification from being implemented when the determined risk level is above a predetermined threshold.
6. The method of claim 2 , wherein the operations further include:
providing the determined risk level as a score from 0 to 100.
7. The method of claim 2 , wherein the system includes at least one of an intake system, a development system, a release system, a deployment system, or an incident reporting system.
8. The method of claim 2 , wherein the proposed modification includes at least one of a modification of a hardware component of the system or a modification of a software component of the system.
9. The method of claim 2 , wherein the operations are performed by using one or more Application Programming Interface (API) interactions.
10. A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method of claim 2 .
11. A computer-implemented system for determining a risk level for a proposed modification to a system, the computer-implemented system comprising:
a memory to store instructions; and
a processor to execute the stored instructions to perform operations including:
receiving metadata regarding the proposed modification to the system;
extracting a feature from the received metadata, the extracted feature corresponding to a feature of a trained machine-learning based model for determining the risk level for the proposed modification based on a learned association between the extracted feature and an incident occurring in the system; and
automatically determining the risk level for the proposed modification based on the extracted feature, by using the trained machine-learning based model that was trained based on a first feature extracted from metadata regarding a previous modification to the system and a second feature extracted from metadata regarding a previous incident related to the previous modification occurring in the system, based on the learned association between the extracted feature and the incident occurring in the system,
wherein the proposed modification includes a modification to code of a software component of the system, and
wherein the operations further include:
determining whether the code is a critical code segment or a non-critical code segment, and
performing at least one of:
providing a suggested action for reducing the determined risk level for the proposed modification when the code is determined to be a non-critical code segment and the determined risk level is above a non-critical code predetermined threshold, or
blocking the proposed modification from being implemented when the code is determined to be a critical code segment and the determined risk level is above a critical code predetermined threshold.
12. The computer-implemented system of claim 11 , wherein the operations further include:
providing an alert identifying the determined risk level for the proposed modification to the system.
13. The computer-implemented system of claim 12 , wherein the providing the alert further includes:
providing a suggested action for reducing the determined risk level for the proposed modification to the system.
14. The computer-implemented system of claim 12 , wherein the providing the alert further includes:
blocking the proposed modification from being implemented when the determined risk level is above a predetermined threshold.
15. The computer-implemented system of claim 11 , wherein the operations further include:
providing the determined risk level as a score from 0 to 100.
16. The computer-implemented system of claim 11 , wherein the system includes at least one of an intake system, a development system, a release system, a deployment system, or an incident reporting system.
17. The computer-implemented system of claim 11 , wherein the proposed modification includes at least one of a modification of a hardware component of the system or a modification of a software component of the system.
18. The computer-implemented system of claim 11 , wherein the operations are performed by using one or more Application Programming Interface (API) interactions.