A system for monitoring exception errors and a method thereof
The system for monitoring exception errors automates log analysis and provides AI-driven recommendations to address critical issues, addressing the challenge of timely error identification and reducing downtime in software applications.
Patent Information
- Application Number
- PCT/IB2023/056836
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-02
- Filing Date
- 2023-06-30
- Publication Date
- 2024-11-07
AI Technical Summary
Software applications often experience disruptions due to unaddressed exception errors, leading to prolonged downtime and revenue loss, as support teams face challenges in timely identification and prioritization of critical log notifications amidst a high volume of notifications.
A system and method for monitoring exception errors, featuring a processing subsystem with modules for automatic log monitoring, exception analysis, source code crawling, alert notification, and artificial intelligence-driven recommendations, to identify and address issues promptly.
The system effectively prioritizes and addresses critical exception errors, reducing downtime and productivity losses by providing timely alerts and actionable insights based on historical data and recency of code changes, thereby enhancing software application reliability.
Smart Images

Figure IB2023056836_07112024_PF_FP_ABST
Abstract
Description
[0001] A SYSTEM FOR MONITORING EXCEPTION ERRORS AND A METHOD THEREOF
[0002] EARLIEST PRIORITY DATE
[0003] This Application claims priority from a Complete patent application filed in India having Patent Application No. 202321031334, filed on May 02, 2023, and titled “A SYSTEM FOR MONITORING EXCEPTION ERRORS AND A METHOD THEREOF”.
[0004] FIELD OF INVENTION
[0005] Embodiments of the present disclosure relate to the field of artificial intelligence, and more particularly, a system for monitoring exception errors and a method thereof.
[0006] BACKGROUND
[0007] With the increasing use of software applications in various industries, it has become crucial to ensure their smooth functioning and availability. However, despite extensive testing and quality assurance measures, errors and exceptions can occur in software applications, causing disruptions, downtime, and significant losses in productivity and revenue.
[0008] As users encounter issues with software applications, they typically escalate issues to the appropriate support teams. One approach that the support team uses to identify and address the error is by analyzing log notifications. However, the identifying and responding to critical log notifications in a timely manner remains a challenge for the support team. Further, with thousands of notifications generated every day, it can be difficult to distinguish between the ones that require immediate attention and those that can be dealt with later. This challenge can lead to delays in resolving issues and result in prolonged downtime, decreased productivity, and revenue loss.
[0009] Hence, there is a need for an improved a system for monitoring exception errors and a method thereof which addresses the aforementioned issue(s).
[0010] BRIEF DESCRIPTION
[0011] In accordance with an embodiment of the present disclosure, a system for monitoring exception errors is provided. The system includes a processing subsystem hosted on a server. The processing subsystem is configured to execute on a network to control bidirectional communications among a plurality of modules. The processing subsystem includes a monitoring module. The monitoring module is configured to monitor a system log automatically to identify one or more log files including one or more exception traces. The one or more exception traces occurs in response to a source code encounters an unexpected one or more error or exception during runtime. The exception trace includes information about the error and corresponding location of the error in the source code. The processing subsystem includes an exception analysis module operatively coupled to the monitoring module. The exception analysis module includes a trace analyzer module configured to parse the one or more exception traces for extracting the information about the error and the corresponding location of the error in the source code based on recency of the error and depth of the exception trace. The exception analysis module further includes a source code crawler module operatively coupled to the trace analyzer module. The source code crawler module is configured to access the source code from a source code repository for each logical unit of the source code including the one or more exception traces identified by the trace analyzer. The source code crawler module is further configured to identify recent code changes in each logical unit of the source code based on recency, configuration, and depth of the one or more exception traces. The processing subsystem includes an alert module operatively coupled to the exception analysis module. The alert module is configured to notify a user about one or more issues in the source code that requires immediate action based on the recent code changes. The alert module further configured to recommend the user with a plurality of subject lines and priorities to take action and address the issues. The processing subsystem includes an artificial intelligence module operatively coupled to the exception analysis module. The artificial intelligence module is configured to analyze a historical data corresponding to the one or more exception traces stored in a database using a machine learning model. The artificial intelligence module is further configured to provide one or more potential actions to be taken on the one or more issues based on historical data. The processing subsystem includes a user interface module operatively coupled to the artificial intelligence module. The user interface module is configured to dynamically alert the user the source code about the exception trace, thereby monitored exception errors.
[0012] In accordance with another embodiment of the present disclosure, a method for monitoring exception errors is provided. The method includes monitoring, by a monitoring module, a system log automatically to identify one or more log files comprising one or more exception traces. The one or more exception traces occurs in response to a source code encounters an unexpected one or more error or exception during runtime. The exception trace includes information about the error and corresponding location of the error in the source code. The method includes parsing, by a trace analyzer module of an exception analysis module, the one or more exception traces for extracting the information about the error and the corresponding location of the error in the source code based on recency of the error and depth of the exception trace. The method includes accessing, by a source code crawler module of the exception analysis module, the source code from a source code repository for each logical unit of the source code including the one or more exception traces identified by the trace analyzer. The method includes identifying, by the source code crawler module of the exception analysis module, recent code changes in each logical unit of the source code based on recency, configuration and depth of the one or more exception traces. The method includes notifying, by an alert module, a user about one or more issues in the source code that requires immediate action based on recent code changes. The method includes recommending, by the alert module, the user with a plurality of subject lines and priorities to take action and address the issues. The method includes analyzing, by an artificial intelligence module, a historical data corresponding to the one or more exception traces stored in a database using a machine learning model. The method includes providing, by the artificial intelligence module, one or more potential actions to be taken on the one or more issues based on historical data. The method includes dynamically alerting, by user interface module the user the source code about the exception trace, thereby monitoring exception errors.
[0013] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will follow by reference to specific embodiments thereof, which are illustrated in the appended figures. It is to be appreciated that these figures depict only typical embodiments of the disclosure and are therefore not to be considered limiting in scope. The disclosure will be described and explained with additional specificity and detail with the appended figures.
[0014] BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The disclosure will be described and explained with additional specificity and detail with the accompanying figures in which: FIG. 1 is a block diagram representation of a system for monitoring exception errors in accordance with an embodiment of the present disclosure;
[0016] FIG. 2 is a block diagram of a computer or a server in accordance with an embodiment of the present disclosure;
[0017] FIG. 3(a) illustrates a flow chart representing the steps involved in a method for monitoring exception errors in accordance with an embodiment of the present disclosure; and
[0018] FIG. 3(b) illustrates continued steps of the method of FIG. 3(a) in accordance with an embodiment of the present disclosure.
[0019] Further, those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.
[0020] DETAILED DESCRIPTION
[0021] For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiment illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.
[0022] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a nonexclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or subsystems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures or additional components. Appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but not necessarily do, all refer to the same embodiment.
[0023] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.
[0024] In the following specification and the claims, reference will be made to a number of terms, which shall be defined to have the following meanings. The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise.
[0025] In accordance with an embodiment of the present disclosure, a system for monitoring exception errors is provided. The system includes a processing subsystem hosted on a server. The processing subsystem is configured to execute on a network to control bidirectional communications among a plurality of modules. The processing subsystem includes a monitoring module. The monitoring module is configured to monitor a system log automatically to identify one or more log files including one or more exception traces. The one or more exception traces occurs in response to a source code encounters an unexpected one or more error or exception during runtime. The exception trace includes information about the error and corresponding location of the error in the source code. The processing subsystem includes an exception analysis module operatively coupled to the monitoring module. The exception analysis module includes a trace analyzer module configured to parse the one or more exception traces for extracting the information about the error and the corresponding location of the error in the source code based on recency of the error and depth of the exception trace. The exception analysis module further includes a source code crawler module operatively coupled to the trace analyzer module. The source code crawler module is configured to access the source code from a source code repository for each logical unit of the source code including the one or more exception traces identified by the trace analyzer. The source code crawler module is further configured to identify recent code changes in each logical unit of the source code based on recency, configuration, and depth of the one or more exception traces. The processing subsystem includes an alert module operatively coupled to the exception analysis module. The alert module is configured to notify a user about one or more issues in the source code that requires immediate action based on the recent code changes. The alert module further configured to recommend the user with a plurality of subject lines and priorities to take action and address the issues. The processing subsystem includes an artificial intelligence module operatively coupled to the exception analysis module. The artificial intelligence module is configured to analyze a historical data corresponding to the one or more exception traces stored in a database using a machine learning model. The artificial intelligence module is further configured to provide one or more potential actions to be taken on the one or more issues based on historical data. The processing subsystem includes a user interface module operatively coupled to the artificial intelligence module. The user interface module is configured to dynamically alert the user the source code about the exception trace, thereby monitoring exception errors.
[0026] FIG. 1 is a block diagram of a system (100) for monitoring exception errors comprising in accordance with an embodiment of the present disclosure. The system (100) includes a processing subsystem (105) hosted on a server (108). In one embodiment, the server (108) may include a cloud-based server. In another embodiment, parts of the server (108) may be a local server coupled to a user device (not shown in FIG.l). The processing subsystem (105) is configured to execute on a network (115) to control bidirectional communications among a plurality of modules. In one example, the network (115) may be a private or public local area network (LAN) or Wide Area Network (WAN), such as the Internet. In another embodiment, the network (115) may include both wired and wireless communications according to one or more standards and / or via one or more transport mediums. In one example, the network (115) may include wireless communications according to one of the 802.11 or Bluetooth specification sets, or another standard or proprietary wireless communication protocol. In yet another embodiment, the network (115) may also include communications over a terrestrial cellular network, including, a global system for mobile communications (GSM), code division multiple access (CDMA), and / or enhanced data for global evolution (EDGE) network.
[0027] The processing subsystem (105) includes a monitoring module (122) to monitor a system log automatically to identify one or more log files that includes one or more exception traces. The system log (120) is a record of operating system events or actions that occur within the operating system. The system log (120) includes a plurality of production logs and environment logs that may help developers to troubleshoot issues and monitor the performance of a system or a software application. The one or more exception traces occurs in response to a source code encounters an unexpected one or more error or exception during runtime, and the exception trace provides information about the error, corresponding location of the error in the source code, type of exception, stack trace and line number of occurrence. The monitoring module (122) is further configured to send the one or more exception traces in real-time. The source code may pertain to any type of software application. Developers may use exception trace to identify and debug issues that arise within the software applications.
[0028] The processing subsystem (105) includes an exception analysis module (124), including a trace analyzer module (126) to parse the one or more exception traces for extracting the information about the error based on recency of the error and depth of the exception trace. The recency of the error may be defined as the frequency of errors that have recently occurred. The recency of the errors may be used to determine the severity of the error. If the error occurred recently, it may be considered a critical issue that requires immediate attention. The recency of the error also considers frequency of occurrence of the error or the impact on system performance. The depth of the exception trace refers to how many deep the error is in the source code.
[0029] The exception analysis module (124) further includes a source code crawler module (128) to access the source code from a source code repository (130) for each logical unit of the source code including the one or more exception traces identified by the trace analyzer module (126). The source code crawler is a type of web crawler. The web crawler is basically a program that is mainly used for navigating to the web and finding new or updated pages for indexing according to specified rules. It may be used for other purposes, such as data mining, web scraping, and website monitoring. The source code crawler module (128) is used to crawl the source code repository for each logical unit involved in the one or more exception traces. The source code repository (130) stores the source code for each logical unit of code identified by the trace analyzer. The source code repository (130) allows developers to track changes, collaborate on code, manage multiple versions of the same codebase, and coordinate the workflow among developers. The examples of source code repository (130) include Git, Subversion, ClearCase, Mercurial, Concurrent Versions System (CVS), Bazaar, Source Code Control System (SCCS) and the like. The source code crawler module (128) is further configured to identify recent code changes in each logical unit of the source code based on recency, configuration, and depth of the one or more exception traces. However, the developers may determine the appropriate actions to address the one or more exception traces.
[0030] The processing subsystem (105) includes an alert module (136) to notify a user about one or more issues in the source code that requires immediate action based on the recent code changes. The user may be developers or a developer community who is developing the source code pertaining to a software application. Further, the user investigates the one or more issues and makes the necessary changes to the code to fix the error. The alert module (136) further recommends the user with a plurality of subject lines and priorities to take action and address the issues. In an embodiment, the alert module (136) is a recency based alert Engine.
[0031] The processing subsystem (105) includes an artificial intelligence module (132) to analyze a historical data corresponding to the one or more exception traces stored in a database (110) using a machine learning model. The database (110) stores information about previous exceptions and corresponding solutions. The machine learning model is configured to identify at least one of corelations, patterns, and similarities between the one or more exception traces. The artificial intelligence module (132) is further configured to provide one or more potential actions to be taken on the one or more issues based on historical data using identified at least one of co-relations, patterns, and similarities between the one or more exception traces.
[0032] The processing subsystem (105) includes a user interface module (134) to dynamically alert the user the source code about the exception trace. In a specific embodiment, the user interface module (134) is an integrated development environment (IDE). The IDE is a software application that provides comprehensive facilities to computer programmers for software development. IDE normally consists of at least a source code editor, build automation tools, and a debugger. Examples of IDE includes, but is not limited to, NetBeans, Eclipse, IntelliJ, Visual Studio, Xcode. In an example, the developer is working on a section of the source code that has had several diagnosed exception traces in the past, the IDE module, alert the developer, providing information about the hotspot and the number of occurrences of the exception trace. So, the developer may investigate the issue and take action to fix the underlying issue before it causes any further issues, thereby monitoring exception errors. It is to be noted that the system may comprise, but is not limited to, a mobile phone, desktop computer, portable digital assistant (PDA), smart phone, tablet, ultra-book, netbook, laptop, multiprocessor system, microprocessor-based or programmable consumer electronic system, or any other communication device that a user may use. In some embodiments, the system may comprise a display module (not shown) to display information (for example, in the form of user interfaces). In further embodiments, the system may comprise one or more of touch screens, accelerometers, gyroscopes, cameras, microphones, global positioning system (GPS) devices, and so forth.
[0033] In one embodiment, the various functional components of the system may reside on a single computer, or they may be distributed across several computers in various arrangements. The various components of the system may, furthermore, access one or more databases, and each of the various components of the system may be in communication with one another. Further, while the components of FIG. 1 are discussed in the singular sense, it will be appreciated that in other embodiments multiple instances of the components may be employed.
[0034] FIG. 2 is a block diagram of a computer or a server in accordance with an embodiment of the present disclosure. The server (200) includes processor(s) (230), and memory (210) operatively coupled to the bus (220). The processor(s) (230), as used herein, means any type of computational circuit, such as, but not limited to, a microprocessor, a microcontroller, a complex instruction set computing microprocessor, a reduced instruction set computing microprocessor, a very long instruction word microprocessor, an explicitly parallel instruction computing microprocessor, a digital signal processor, or any other type of processing circuit, or a combination thereof.
[0035] The memory (210) includes several subsystems stored in the form of executable program which instructs the processor (230) to perform the method steps illustrated in FIG. 1. The memory (210) includes a processing subsystem (105) of FIG.1. The processing subsystem (105) further has the following modules: a monitoring module (122), an exception analysis module (124), an alert module (136), an artificial intelligence module (132) and user-interface module.
[0036] In accordance with an embodiment of the present disclosure, a system for monitoring exception errors is provided. The system includes a processing subsystem (105) hosted on a server. The processing subsystem (105) is configured to execute on a network to control bidirectional communications among a plurality of modules. The processing subsystem (105) includes a monitoring module (122). The monitoring module (122) is configured to monitor a system log (120) automatically to identify one or more log files including one or more exception traces. The one or more exception traces occurs in response to a source code encounters an unexpected one or more error or exception during runtime. The exception trace includes information about the error and corresponding location of the error in the source code. The processing subsystem (105) includes an exception analysis module (124) operatively coupled to the monitoring module (122). The exception analysis module (124) includes a trace analyzer module (126) configured to parse the one or more exception traces for extracting the information about the error and the corresponding location of the error in the source code based on recency of the error and depth of the exception trace. The exception analysis module (124) further includes a source code crawler module (128) operatively coupled to the trace analyzer module (126). The source code crawler module (128) is configured to access the source code from a source code repository (130) for each logical unit of the source code including the one or more exception traces identified by the trace analyzer. The source code crawler module (128) is further configured to identify recent code changes in each logical unit of the source code based on recency, configuration, and depth of the one or more exception traces. The processing subsystem (105) includes an alert module (136) operatively coupled to the exception analysis module (124). The alert module (136) is configured to notify a user about one or more issues in the source code that requires immediate action based on the recent code changes. The alert module (136) further configured to recommend the user with a plurality of subject lines and priorities to take action and address the issues. The processing subsystem (105) includes an artificial intelligence module (132) operatively coupled to the exception analysis module (124). The artificial intelligence module (132) is configured to analyze a historical data corresponding to the one or more exception traces stored in a database (110) using a machine learning model. The artificial intelligence module ( 132) is further configured to provide one or more potential actions to be taken on the one or more issues based on historical data. The processing subsystem (105) includes a user interface module (134) operatively coupled to the artificial intelligence module (132). The user interface module (134) is configured to dynamically alert the user the source code about the exception trace, thereby monitoring exception errors.
[0037] The bus (220) as used herein refers to be internal memory channels or computer network that is used to connect computer components and transfer data between them. The bus (220) includes a serial bus or a parallel bus, wherein the serial bus transmits data in bit-serial format and the parallel bus transmits data across multiple wires. The bus (220) as used herein, may include but not limited to, a system bus, an internal bus, an external bus, an expansion bus, a frontside bus, a backside bus and the like.
[0038] FIG. 3(a) illustrates a flow chart representing the steps involved in a method for monitoring exception errors in accordance with an embodiment of the present disclosure. The method (300) includes monitoring, by a monitoring module, a system log automatically to identify one or more log files comprising one or more exception traces. The monitoring module continuously monitors the system log that includes a plurality of production logs and environment logs that may help developers to troubleshoot issues and monitor the performance of a system or a software application. The one or more exception traces occurs in response to a source code encounters an unexpected one or more error or exception during runtime. The exception trace includes information about the error and corresponding location of the error in the source code in step 310. The source code may pertain to any type of software application. Developers may use exception trace to identify and debug issues that arise within the software applications.
[0039] The method (300) includes parsing, by a trace analyzer module of an exception analysis module, the one or more exception traces for extracting the information about the error and the corresponding location of the error in the source code based on recency of the error and depth of the exception trace in step 32O.The parsing is a process of analyzing and interpreting the syntax of a program or a data structure to extract relevant information. In the process, the system log that contains one or more exception traces breaks down into individual components to extract relevant information from these components. The recency of the error refers to how recently the error occurred. The recency of the errors may be used to determine the severity of the error. If an error occurred recently, it may be considered a critical issue that requires immediate attention. The recency of the error also considers frequency of occurrence of the error or the impact on system performance. The depth of the exception trace refers to how many deep the error is in the source code.
[0040] The method (300) includes accessing, by a source code crawler module of the exception analysis module, the source code from a source code repository for each logical unit of the source code including the one or more exception traces identified by the trace analyzer in step 330. The source code crawler module is used to crawl the source code repository for each logical unit involved in the one or more exception traces. The source code repository stores the source code for each logical unit of code identified by the trace analyzer. The source code repository allows developers to track changes, collaborate on code, manage multiple versions of the same codebase, and coordinate the workflow among developers. The examples of source code repository include Git, Subversion, ClearCase, Mercurial, Concurrent Versions System (CVS), Bazaar, Source Code Control System (SCCS) and the like.
[0041] The method (300) includes identifying, by the source code crawler module of the exception analysis module, recent code changes in each logical unit of the source code based on recency, configuration, and depth of the one or more exception traces in step 340. However, the developers may determine the appropriate actions to address the one or more exception traces.
[0042] The method (300) includes notifying, by an alert module, a user about one or more issues in the source code that requires immediate action based on recent code changes in step 350.The user may be developers or a developer community who is developing corresponding software application. Further, the user investigates the one or more issues and makes the necessary changes to the code to fix the error.
[0043] FIG. 3(b) illustrates continued steps of the method of FIG. 3(a) in accordance with an embodiment of the present disclosure.
[0044] The method (300) includes recommending, by the alert module, the user with a plurality of subject lines and priorities to take action and address the issues in step 360. In an embodiment, the alert module is a recency based alert Engine.
[0045] The method (300) includes analyzing, by an artificial intelligence module, a historical data corresponding to the one or more exception traces stored in a database using a machine learning model in step 370. This machine learning model will learn on its own over a period and give smart suggestions. The database stores information about previous exceptions and corresponding solutions. The machine learning model is configured to identify at least one of co-relations, patterns, and similarities between the one or more exception traces. The method (300) includes providing, by the artificial intelligence module, one or more potential actions to be taken on the one or more issues based on historical data in step 380.
[0046] The method (300) includes dynamically alerting, by a user interface module the user the source code about the exception trace, thereby monitoring exception errors in step 390. In a specific embodiment, the user interface module is an integrated development environment (IDE). The IDE normally consists of at least a source code editor, build automation tools, and a debugger. Examples of IDE includes NetBeans, Eclipse, IntelliJ, Visual Studio, Xcode and the like. With the user interface the developer may investigate the issue and take action to fix the underlying issue before it causes any further issues, thereby monitoring exception errors.
[0047] Various embodiments of the system and method for monitoring exception errors as described above leverages coding and is highly scalable across market segments, industries, and has several advantages. It ensures consistency in a software development process and facilitates collaboration between the developers and developer community. Further, the system provides easy reporting of hotspots and vulnerable areas to development teams based on historical data by the use of a machine learning module and artificial intelligence. It helps to reduce the risk of critical issues raising in the software application. Furthermore, the system is super important in identifying critical issues before going into production. By proactively monitoring and analyzing exception traces and other system logs, the system can identify potential issues that may cause problems in production.
[0048] The techniques described in this disclosure may be implemented, at least in part, in hardware, software, firmware, or any combination thereof. For example, various aspects of the described techniques may be implemented within one or more processors, including one or more microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components. The term “processor” or “processing subsystem” may generally refer to any of the foregoing logic circuitry, alone or in combination with other logic circuitry, or any other equivalent circuitry. A control unit including hardware may also perform one or more of the techniques of this disclosure. Such hardware, software, and firmware may be implemented within the same device or within separate devices to support the various techniques described in this disclosure. In addition, any of the described units, modules, or components may be implemented together or separately as discrete but interoperable logic devices. Depiction of different features as modules or units is intended to highlight different functional aspects and does not necessarily imply that such modules or units must be realized by separate hardware, firmware, or software components. Rather, functionality associated with one or more modules or units may be performed by separate hardware, firmware, or software components, or integrated within common or separate hardware, firmware, or software components.
[0049] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the disclosure and are not intended to be restrictive thereof.
[0050] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person skilled in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.
[0051] The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, the order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.
Claims
CLAIM:
1. A system (100) monitoring exception errors comprising: a processing subsystem (105) hosted on a server, wherein the processing subsystem (105) is configured to execute on a network to control bidirectional communications among a plurality of modules comprising: a monitoring module (122) is configured to monitor a system log (120) automatically to identify one or more log files comprising one or more exception traces, wherein the one or more exception traces occurs in response to a source code encounters an unexpected one or more error or exception during runtime, wherein the exception trace comprises information about the error and corresponding location of the error in the source code; an exception analysis module (124) operatively coupled to the monitoring module (122), wherein the exception analysis module (124) comprises: a trace analyzer module (126) is configured to parse the one or more exception traces for extracting the information about the error and the corresponding location of the error in the source code based on recency of the error and depth of the exception trace; a source code crawler module (128) operatively coupled to the trace analyzer module (126), wherein the source code crawler module (128) is configured to: access the source code from a source code repository (130) for each logical unit of the source code comprising the one or more exception traces identified by the trace analyser; and identify recent code changes in each logical unit of the source code based on recency, configuration and depth of the one or more exception traces;an alert module (136) operatively coupled to the exception analysis module (124), wherein the alert module (136) is configured to: notify a user about one or more issues in the source code that requires immediate action based on recent code changes; and recommend the user with a plurality of subject lines and priorities to take action and address the issues; an artificial intelligence module (132) operatively coupled to the exception analysis module (124), wherein the artificial intelligence module (132) is configured to: analyze a historical data corresponding to the one or more exception traces stored in a database (110) using a machine learning model; and provide one or more potential actions to be taken on the one or more issues based on historical data; and a user interface module (134) operatively coupled to the artificial intelligence module (132), wherein the user interface module (134) is configured to dynamically alert the user the source code about the exception trace, thereby monitored exception errors.
2. The system (100) as claimed in claiml, wherein the system log (120) comprises a plurality of production logs and environment logs.
3. The system (100) of claim 1 , wherein the exception trace comprises information about type of exception, stack trace and line number of occurrence.
4. The system (100) of claim 1, wherein the monitoring module (122) is configured to send the one or more exception traces to the exception analysis module (124) in real-time.
5. The system (100) of claim 1, wherein the source code repository (130) stores the source code for each logical unit of code identified by the trace analyzer module.
6. The system (100) of claim 1 , wherein the database (110) stores information about previous exceptions and corresponding solutions.
7. The system (100) of claim 1, wherein the source code crawler module (128) is configured to prioritize accessing the source code based on the depth of the exception trace.
8. The system (100) of claim 1, wherein the integrated development environment module is configured to provide context-sensitive suggestions based on the exception trace.
9. The system (100) of claim 1, wherein the machine learning model is configured to identify at least one of co-relations, patterns, and similarities between the one or more exception traces.
10. A method (300) for monitoring exception errors comprising: monitoring, by a monitoring module, a system log automatically to identify one or more log files comprising one or more exception traces, wherein the one or more exception traces occurs in response to a source code encounters an unexpected one or more error or exception during runtime, wherein the exception trace comprises information about the error and corresponding location of the error in the source code; (310) parsing, by a trace analyzer module of an exception analysis module, the one or more exception traces for extracting the information about the error and the corresponding location of the error in the source code based on recency of the error and depth of the exception trace; (320) accessing, by a source code crawler module of the exception analysis module, the source code from a source code repository for each logical unit of the source code comprising the one or more exception traces identified by the trace analyzer; (330) identifying, by the source code crawler module of the exception analysis module, recent code changes in each logical unit of the source code based on recency, configuration and depth of the one or more exception traces; (340) notifying, by an alert module, a user about one or more issues in the source code that requires immediate action based on recent code changes; (350) recommending, by the alert module, the user with a plurality of subject lines and priorities to take action and address the issues; (360)analysing, by an artificial intelligence module, a historical data corresponding to the one or more exception traces stored in a database using a machine learning model; (370) providing, by the artificial intelligence module, one or more potential actions to be taken on the one or more issues based on historical data; and (380) dynamically alerting, by user interface module the user the source code about the exception trace, thereby monitored exception errors. (390)
Citation Information
Patent Citations
Automatic debugging method and system for software and hardware co-simulation
CN115357511A
System and method for automatically identifying and resolving computing errors
US11366713B2
