18094380. PROVIDING EXPLANATION OF NETWORK INCIDENT ROOT CAUSES simplified abstract (VMWARE, INC.)
Contents
- 1 PROVIDING EXPLANATION OF NETWORK INCIDENT ROOT CAUSES
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 PROVIDING EXPLANATION OF NETWORK INCIDENT ROOT CAUSES - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Unanswered Questions
- 1.11 Original Abstract Submitted
PROVIDING EXPLANATION OF NETWORK INCIDENT ROOT CAUSES
Organization Name
Inventor(s)
Wenxuan Zhou of Santa Clara CA (US)
Radhika Niranjan Mysore of Cupertino CA (US)
Philip Brighten Godfrey of Champaign IL (US)
Sujata Banerjee of Palo Alto CA (US)
PROVIDING EXPLANATION OF NETWORK INCIDENT ROOT CAUSES - A simplified explanation of the abstract
This abstract first appeared for US patent application 18094380 titled 'PROVIDING EXPLANATION OF NETWORK INCIDENT ROOT CAUSES
Simplified Explanation
Some embodiments provide a method for reporting potential root causes of incidents within a network. The method identifies a first network entity as a potential root cause of an incident affecting a second network entity. For each network entity of a set of network entities in a dependency chain beginning with the first network entity and ending with the second network entity, the method assigns a label to the network entity based on measured metrics of the network entity. The method uses a state machine that encodes causality between different network entity labels to generate a human-readable explanation for the first network entity causing the incident affecting the second network entity.
- Method for reporting potential root causes of incidents within a network
- Identification of potential root causes based on measured metrics of network entities
- Use of a state machine to generate human-readable explanations for causality between network entities
Potential Applications
This technology could be applied in network troubleshooting and incident response systems to quickly identify and address root causes of network incidents.
Problems Solved
This technology helps in efficiently identifying and resolving network incidents by pinpointing potential root causes based on measured metrics of network entities.
Benefits
- Faster incident resolution in network environments - Improved network performance and reliability - Enhanced understanding of network dependencies
Potential Commercial Applications
Optimizing network operations in large enterprises, improving service reliability in telecommunications companies, enhancing cybersecurity incident response capabilities.
Possible Prior Art
One possible prior art could be the use of network monitoring tools that track network performance metrics to identify potential issues and root causes of incidents.
Unanswered Questions
How does this method handle complex network dependencies with multiple potential root causes?
The method uses a state machine to encode causality between different network entity labels, but it is unclear how it deals with scenarios where multiple network entities could be contributing to an incident.
What are the limitations of this method in large-scale network environments?
It is not specified how this method scales in large and complex network environments with a high number of network entities and dependencies.
Original Abstract Submitted
Some embodiments provide a method for reporting potential root causes of incidents within a network. The method identifies a first network entity as a potential root cause of an incident affecting a second network entity. For each network entity of a set of network entities in a dependency chain beginning with the first network entity and ending with the second network entity, the method assigns a label to the network entity based on measured metrics of the network entity. The method uses a state machine that encodes causality between different network entity labels to generate a human-readable explanation for the first network entity causing the incident affecting the second network entity.
