Error positioning method and apparatus for information system, and electronic device and storage medium

Abstract

An error positioning method and apparatus for an information system, and an electronic device and a storage medium. The method and apparatus are applied to an electronic device, and the method specifically comprises: acquiring fault information by monitoring an upstream system; acquiring effective error reporting data on the basis of the fault information; performing analysis processing on the error reporting data to obtain error information; and feeding back the error information to the upstream system. By means of the method, corresponding error information can be obtained by monitoring the upstream system and automatically analyzing the obtained information. Compared with a manual mode, the method is faster and more accurate, and improves the error positioning efficiency.

Description

Information system error positioning method, device, electronic device and storage medium

[0001] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on March 20, 2024, with application number 202410323191.9 and application name “A method, device, electronic device and storage medium for error location in an information system”, the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0002] The present application relates to the field of information technology, and more particularly to an error location method for an information system. Background Art

[0003] With the development of the internet and big data technologies, the data volume and business complexity of information systems across various industries are growing exponentially. For example, the civil aviation industry generates massive amounts of flight data and passenger transaction data daily, along with data generated by complex business processes such as ticket changes, refunds, and flight adjustments. This massive amount of heterogeneous data makes the operation and maintenance of civil aviation transaction computing systems extremely difficult. Once a system error occurs, locating and resolving the issue requires significant manpower and time.

[0004] Currently, information systems typically rely on manual analysis to locate problems by reading and analyzing log files. However, log formats vary across different information systems, making manual interpretation time-consuming and inefficient. Therefore, there is an urgent need for a solution that can quickly parse system logs and automatically analyze and locate errors. Summary of the Invention

[0005] In view of this, the present application provides an information system error location method, device, electronic device and storage medium, which are used to replace manual methods to locate errors in the information system.

[0006] In order to achieve the above objectives, the following solutions are proposed:

[0007] An information system error location method is applied to electronic equipment, and the error location method comprises the following steps:

[0008] Obtain fault information by monitoring the upstream system;

[0009] Obtaining valid error reporting data according to the fault information;

[0010] Analyzing and processing the error reporting data to obtain error information;

[0011] Feedback the error information to the upstream system.

[0012] Optionally, the fault information includes the fault time and interface information of the faulty interface.

[0013] Optionally, obtaining valid error reporting data according to the fault information includes the steps of:

[0014] The service data of the faulty interface within a fixed time period is acquired by querying a database, where the fault time is included in the fixed time period.

[0015] Optionally, analyzing and processing the error reporting data to obtain error information includes the following steps:

[0016] Calculating and processing the error data to obtain one or more initial error codes;

[0017] A database query operation is performed based on the one or more initial error codes to obtain the error information.

[0018] Optionally, the calculating and processing the error data to obtain one or more initial error codes comprises the following steps:

[0019] Perform query processing based on the error data to obtain multiple error codes to be selected;

[0020] Calculating the occurrence frequency of each of the error codes to be selected according to the type of the error codes to be selected;

[0021] The one or more candidate error codes with the highest occurrence frequency are determined as the initial error codes.

[0022] Optionally, the error information is a data frame, which includes part or all of the date, api_name, transaction ID, ErrorCode and NewErrorCode corresponding to the fault port in the database.

[0023] Optionally, feeding back the error information to the upstream system comprises the steps of:

[0024] Formatting the error information to obtain formatted error information;

[0025] Feedback the formatting error information to the upstream system.

[0026] An error locating device for an information system, applied to an electronic device, comprising:

[0027] A data monitoring module is configured to obtain fault information by monitoring the upstream system;

[0028] A data acquisition module is configured to acquire valid error reporting data according to the fault information;

[0029] A data analysis module is configured to analyze and process the error reporting data to obtain error information;

[0030] The information feedback module is configured to feed back the error information to the upstream system.

[0031] An electronic device comprising at least one processor and a memory connected to the processor, wherein:

[0032] The memory is used to store computer programs or instructions;

[0033] The processor is configured to execute the computer program or instruction so as to enable the electronic device to implement the error positioning method as described above.

[0034] A storage medium is applied to an electronic device, wherein the storage medium carries one or more computer programs, and the one or more computer programs can be executed by the electronic device, thereby enabling the electronic device to implement the error location method as described above.

[0035] As can be seen from the above technical solutions, this application discloses a method, device, electronic device, and storage medium for locating errors in an information system. This method and device, applied to electronic devices, specifically involves monitoring an upstream system to obtain fault information; obtaining valid error reporting data based on the fault information; analyzing and processing the error reporting data to obtain error information; and feeding the error information back to the upstream system. This solution obtains corresponding error information by monitoring upstream information and automatically analyzing the obtained information. Compared to manual methods, this method is faster and more accurate, improving the efficiency of error locating.

[0036] In summary, this solution has the following effects:

[0037] 1. Reduced fault location time - Quickly locking the error code can significantly reduce the time it takes for operation and maintenance personnel to confirm the root cause of the problem, thereby reducing operation and maintenance costs.

[0038] 2. It can shorten the system's fault response time - it can locate the cause of the fault in the first place, allowing operation and maintenance personnel to respond quickly, thereby reducing system downtime

[0039] 3. Improve repair efficiency - With error code information, operation and maintenance personnel can directly check the solution without having to repeatedly locate the problem, thus optimizing the repair process.

[0040] 4. Ability to reduce the scope of fault impact - By quickly locating the root cause of the fault, further spread of the fault can be avoided and the scope of business interruption can be reduced.

[0041] 5. Reduce reliance on professional skills - Error code information makes fault handling standardized and queryable, reducing reliance on professional skilled personnel and reducing labor costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0043] FIG1 is a flow chart of a method for locating an error in an information system according to an embodiment of the present application;

[0044] FIG2 is a block diagram of an error location device for an information system according to an embodiment of the present application;

[0045] FIG3 is a block diagram of another error location device of an information system according to an embodiment of the present application;

[0046] FIG4 is a schematic diagram of an interface of an error code front-end maintenance module in an embodiment of the present application;

[0047] FIG5 is a block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0048] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0049] To address the shortcomings of the existing traditional manual data query and error location methods, this invention utilizes the unified interface classification, definition, encapsulation, and publishing features, and uses a fully humanized search process and location logic to quickly search for initial error codes in a large number of input and output requests, and use multi-dimensional comparison to locate the initial error code with the highest probability of causing the fault. This shortens the time spent on troubleshooting, improves the efficiency of locating the root cause, reduces the impact on users, and improves service quality. Specific implementation methods are as follows:

[0050] FIG1 is a flowchart of an error location method for an information system according to an embodiment of the present application.

[0051] As shown in FIG1 , the error location method provided in this embodiment is applied to an electronic device to replace manual methods for locating errors in an information system. The electronic device can be understood as a computer, server, or cloud platform with data computing and information processing capabilities. The error location method includes the following steps:

[0052] S1. Obtain fault information by monitoring the upstream system.

[0053] The execution process includes starting the corresponding API service and monitoring upstream requests. During the monitoring process, the upstream information call information, call information time format, and interface format are verified to ensure they are correct. If the verification determines an error has occurred, the fault information is generated. The fault information includes the time the fault occurred and the interface information of the faulty interface.

[0054] S2. Obtain valid error reporting data based on the fault information.

[0055] After determining the fault information, we can retrieve the error data based on the fault time and interface information of the faulty interface. Specifically, we obtain an accurate time node and one or N interface information from the upstream system. We then define a time period around this accurate time, such as starting 30 minutes ago and ending 10 minutes in the future. We then query the Elsticsearch database, the data source, using the interface information and failed request status as query criteria. The resulting data is cleaned and filtered to generate a DataFrame containing information such as date, api_name, transaction ID, ErrorCode, and NewErrorCode. This data is then compared with the same period data obtained 7 and 14 days prior.

[0056] S3. Analyze and process the error data to obtain error information.

[0057] Specifically, the error data is processed to obtain one or more initial error codes, which are then used to query the database to obtain error information. For example, the current and historical DataFrames obtained can be used to count the types and numbers of all initial error codes that occurred during a specific time period.

[0058] First, we divide initial error codes into two categories: the first category is initial error codes that have not appeared at the same time point in history, and are temporarily considered to be error codes with a high incidence of current faults. The second category is initial error codes that have appeared at the same time point in history, and these initial error codes need to be discussed separately.

[0059] Secondly, the occurrence of the second type of error code requires building a simple decision tree model based on the probability of the initial error code appearing in a large amount of historical data. This can filter out some errors that may also occur under normal circumstances. Therefore, the frequency of occurrence of the initial error code needs to be stratified, as shown in the following table:

[0060] set up:

[0061] x = the number of times the current error code occurs

[0062] σ=Number of error codes that occurred during the same period seven days ago

[0063] β=Number of error codes that occurred during the same period fourteen days ago

[0064] μ=abnormal probability threshold

[0065] but:

[0066] 1) Calculate the average number of error codes in the past two weeks: γ=(σ+β) / 2

[0067] 2) Calculate the growth rate: f(x) = (x-γ) / γ

[0068] 3) Determine the relationship between f(x) and threshold μ:

[0069] If f(x)>μ, then the probability of x occurring is abnormal;

[0070] If f(x)<=μ, it means that x appears normal.

[0071] Through this method, we can use the statistical laws of the same period in the past to determine whether the frequency of the current error code is abnormal.

[0072] The following is an explanation through specific examples.

[0073] Example 1:

[0074] Failure time: 7:39 am, July 4, 2023

[0075] Failed interface information: ModifyPassengerInfoOpen and DocumentCheckopen

[0076] 1) The data collection module calculates the current start_time: "2023-07-04 07:09:00" and end_time: "2023-07-04 07:49:00" based on "July 4, 2023 7:39 AM." Seven days ago, the start_time: "2023-06-27 07:09:00" and end_time: "2023-06-27 07:49:00." Fourteen days ago, the start_time: "2023-06-20 07:09:00" and end_time: "2023-06-20 07:49:00." Using this time range as the search criteria, the ModifyPassengerInfoOpen and DocumentCheckopen interfaces of the corresponding Elsticsearch database are queried. The resulting JSON information is cleaned and filtered. Three different CSV files are generated and returned to the error code logic calculation and location module.

[0077] 2) The error code logic calculation and positioning module reads three CSV files and analyzes and counts all the initial error code data. Substitute the above calculation formula to calculate f(x), for example:

[0078] Initial error code: XX-0410-08

[0079] x=85 (number of times the current error code occurs)

[0080] σ=47 (number of error code occurrences 7 days ago)

[0081] β=33 (number of error code occurrences 14 days ago)

[0082] Calculate the average number of error code occurrences: γ=(σ+β) / 2=(47+33) / 2=40 Calculate the growth rate: f(x)=(X-γ) / γ=(85-40) / 40=45 / 40=1.125 According to Table 1, μ=0.75

[0083] f(x)=1.125>μ=0.75 means that the number of occurrences of the current error code XX-0410-08 has increased significantly compared to the average level, which is likely to represent an abnormal state.

[0084] 3) The error code information query module is then called to query the database using the query criteria XX-0410-08, formatting the retrieved information. Finally, the information is sorted by exception rate and returned to the upstream system to complete the rapid retrieval and location of the initial error code.

[0085] Example 2:

[0086] Failure time: 7:39 am, July 4, 2023

[0087] Failure interface information: DocumentCompletenessCheck

[0088] 1) The data acquisition module calculates the current start_time: "2023-07-04 07:09:00" and end_time: "2023-07-04 07:49:00" based on "July 4, 2023 7:39 AM." Seven days ago, the start_time: "2023-06-27 07:09:00" and end_time: "2023-06-27 07:49:00." Fourteen days ago, the start_time: "2023-06-20 07:09:00" and end_time: "2023-06-20 07:49:00." Using this time range as the search criteria, the Elsticsearch database's DocumentCompletenessCheck interface is queried. The resulting JSON information is cleaned and filtered. Three different CSV files are generated and returned to the error code logic calculation and location module.

[0089] 2) The error code logic calculation and positioning module reads three CSV files and analyzes and counts all the initial error code data. Substitute the above calculation formula to calculate f(x), for example:

[0090] Initial error code: XX-0320-09

[0091] x=46 (number of times the current error code occurs)

[0092] σ=47 (number of error code occurrences 7 days ago)

[0093] β=33 (number of error code occurrences 14 days ago)

[0094] Calculate the average number of error code occurrences: γ = (σ + β) / 2 = (47 + 33) / 2 = 40

[0095] Calculate the growth rate: f(x) = (X-γ) / γ = (46-40) / 40 = 45 / 40 = 0.15 According to Table 1, μ = 0.9

[0096] f(x)=0.15<μ=0.9 means that the current error code XX-0320-09 growth rate is positive but within the range of 0.9, indicating that the number of occurrences of the current error code has increased but is still a normal change.

[0097] S4. Feedback error information to the upstream system.

[0098] After the error information is determined, the error information can be fed back to the upstream information through a preset means. When feeding back, the error information is first formatted to obtain formatted error information, and then the formatted error information is fed back to the upstream system.

[0099] As can be seen from the above technical solution, this embodiment provides a method for locating errors in an information system, applicable to electronic devices. Specifically, the method comprises monitoring upstream systems to obtain fault information; obtaining valid error reporting data based on the fault information; analyzing and processing the error reporting data to obtain error information; and feeding the error information back to the upstream system. This solution obtains the corresponding error information by monitoring upstream information and automatically analyzing the obtained information. Compared to manual methods, this method is faster and more accurate, improving the efficiency of error location.

[0100] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0101] Although the operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order.Multitasking and parallel processing may be advantageous under certain circumstances.

[0102] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0103] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as C or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer.

[0104] FIG2 is a block diagram of an error location device for an information system according to an embodiment of the present application.

[0105] As shown in Figure 2, the error location device provided in this embodiment is applied to an electronic device to replace manual methods to locate errors in the information system. The electronic device can be understood as a computer, server or cloud platform with data computing and information processing capabilities. The error location device includes a data monitoring module 10, a data acquisition module 20, a data analysis module 30 and an information feedback module 40.

[0106] The data monitoring module is used to obtain fault information by monitoring the upstream system.

[0107] The execution process includes starting the corresponding API service and monitoring upstream requests. During the monitoring process, the upstream information call information, call information time format, and interface format are verified to ensure they are correct. If the verification determines an error has occurred, the fault information is generated. The fault information includes the time the fault occurred and the interface information of the faulty interface.

[0108] The data acquisition module is used to obtain valid error data based on fault information.

[0109] After determining the fault information, error data can be retrieved based on the fault time and interface information of the faulty interface. Specifically, an accurate time node and one or N interface information are obtained from the upstream system. A time period is determined around this accurate time, such as starting 30 minutes ago and ending 10 minutes in the future. The Elsticsearch database of the corresponding data source 100 is queried using the interface information and failed request status as query criteria. The resulting data is cleaned and filtered to generate a DataFrame containing information such as date, api_name, transaction ID, ErrorCode, and NewErrorCode. This data is then compared with the same period data obtained 7 and 14 days ago.

[0110] The data analysis module is used to analyze and process the error data to obtain error information.

[0111] Specifically, the error data is processed to obtain one or more initial error codes, and then a database query operation is performed based on the one or more initial error codes to obtain error information from database 200. For example, the types and numbers of all initial error codes occurring within the time period are counted using the obtained current and historical DataFrames.

[0112] First, we divide initial error codes into two categories: the first category is initial error codes that have not appeared at the same time point in history, and are temporarily considered to be error codes with a high incidence of current faults. The second category is initial error codes that have appeared at the same time point in history, and these initial error codes need to be discussed separately.

[0113] Secondly, the occurrence of the second type of error code requires building a simple decision tree model based on the probability of the initial error code appearing in a large amount of historical data. This can filter out some errors that may also occur under normal circumstances. Therefore, the frequency of occurrence of the initial error code needs to be stratified, as shown in the following table:

[0114] set up:

[0115] x = the number of times the current error code occurs

[0116] σ=Number of error codes that occurred during the same period seven days ago

[0117] β=Number of error codes that occurred during the same period fourteen days ago

[0118] μ=abnormal probability threshold

[0119] but:

[0120] 1) Calculate the average number of error codes in the past two weeks: γ=(σ+β) / 2

[0121] 2) Calculate the growth rate: f(x) = (x-γ) / γ

[0122] 3) Determine the relationship between f(x) and threshold μ:

[0123] If f(x)>μ, then the probability of x occurring is abnormal;

[0124] If f(x)<=μ, it means that x appears normal.

[0125] Through this method, we can use the statistical laws of the same period in the past to determine whether the frequency of the current error code is abnormal.

[0126] The information feedback module is used to feed back error information to the upstream system.

[0127] After the error information is determined, the error information can be fed back to the upstream information through a preset means. When feeding back, the error information is first formatted to obtain formatted error information, and then the formatted error information is fed back to the upstream system.

[0128] As can be seen from the above technical solution, this embodiment provides an information system error location device, applicable to electronic devices. Specifically, the device monitors upstream systems to obtain fault information; obtains valid error reporting data based on the fault information; analyzes and processes the error reporting data to obtain error information; and feeds the error information back to the upstream system. This solution monitors upstream information and automatically analyzes the obtained information to obtain the corresponding error information. Compared to manual methods, this solution is faster and more accurate, improving the efficiency of error location.

[0129] In addition, this embodiment also includes an error code front-end maintenance module 300 and an error code back-end maintenance module 400, as shown in Figure 3. The error code maintenance front-end module is used to maintain and manage information such as error codes, initial error codes, software codes, internal error information, and external error information through a visual interface, as shown in Figure 4. The error code back-end maintenance module is used to provide API services for the error code front-end maintenance module, read and write to the database, and complete the addition, deletion, modification, and query of initial error code information.

[0130] The units involved in the embodiments described in this disclosure may be implemented in software or hardware. In some cases, the name of a unit does not limit the unit itself. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses."

[0131] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0132] FIG5 is a block diagram of an electronic device according to an embodiment of the present application.

[0133] Reference is now made to FIG5 , which illustrates a schematic diagram of an electronic device suitable for implementing the embodiments of the present disclosure. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. This electronic device is merely an example and should not limit the functionality and scope of use of the embodiments of the present disclosure.

[0134] The electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory ROM 502 or a program loaded from an input device 506 into a random access memory RAM 503. Various programs and data required for the operation of the electronic device are also stored in the RAM. The processing device, ROM, and RAM are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0135] Typically, the following devices may be connected to the I / O interface: input devices such as a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 507 such as a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 508 such as a magnetic tape, hard disk, etc.; and communication devices 509. Communication devices 509 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although the figures illustrate electronic devices with various devices, it should be understood that not all of the devices shown are required to be implemented or present. More or fewer devices may be implemented or present instead.

[0136] The present application also provides a computer-readable storage medium embodiment.

[0137] The aforementioned storage medium is applied to an electronic device and carries one or more computer programs. When executed by the electronic device, the electronic device monitors upstream systems to obtain fault information; obtains valid error data based on the fault information; analyzes and processes the error data to obtain error information; and then feeds the error information back to the upstream system. This solution obtains corresponding error information by monitoring upstream information and automatically analyzing the obtained information. Compared to manual methods, this solution is faster and more accurate, improving the efficiency of error location.

[0138] It should be noted that the computer-readable medium disclosed herein may be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0139] In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

[0140] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0141] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they are aware of the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0142] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or terminal device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that includes the element.

[0143] The technical solution provided by the present invention is introduced in detail above. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting the present invention. Industrial Applicability

[0144] The present disclosure provides an information system error location method, device, electronic device, and storage medium. The method and device are applied to electronic devices and specifically involve monitoring upstream systems to obtain fault information; obtaining valid error reporting data based on the fault information; analyzing and processing the error reporting data to obtain error information; and feeding the error information back to the upstream system. This solution, which monitors upstream information and automatically analyzes the obtained information to obtain the corresponding error information, is faster and more accurate than manual methods, improving the efficiency of error location.

Claims

1. A method for locating an error in an information system, applied to an electronic device, comprising the steps of: Obtain fault information by monitoring the upstream system; Obtaining valid error reporting data according to the fault information; Analyzing and processing the error reporting data to obtain error information; Feedback the error information to the upstream system.

2. The error location method according to claim 1, wherein: The fault information includes the fault time and the interface information of the fault interface.

3. The error location method according to claim 2, wherein: The method of obtaining valid error reporting data according to the fault information comprises the steps of: The service data of the faulty interface within a fixed time period is acquired by querying a database, where the fault time is included in the fixed time period.

4. The error location method according to claim 1, wherein: The step of analyzing and processing the error reporting data to obtain error information comprises the following steps: Calculating and processing the error data to obtain one or more initial error codes; A database query operation is performed based on the one or more initial error codes to obtain the error information.

5. The error location method according to claim 4, wherein: The calculating and processing the error data to obtain one or more initial error codes comprises the following steps: Perform query processing based on the error data to obtain multiple error codes to be selected; Calculating the occurrence frequency of each of the error codes to be selected according to the type of the error codes to be selected; The one or more candidate error codes with the highest occurrence frequency are determined as the initial error codes.

6. The error location method according to claim 4, wherein: The error information is a data frame, which includes part or all of the date, api_name, transaction ID, ErrorCode and NewErrorCode corresponding to the fault port in the database.

7. The error location method according to claim 1, wherein: Feedback of the error information to the upstream system comprises the following steps: Formatting the error information to obtain formatted error information; Feedback the formatting error information to the upstream system.

8. An error locating device for an information system, applied to an electronic device, the error locating device comprising: A data monitoring module is configured to obtain fault information by monitoring the upstream system; A data acquisition module is configured to acquire valid error reporting data according to the fault information; A data analysis module is configured to analyze and process the error reporting data to obtain error information; The information feedback module is configured to feed back the error information to the upstream system.

9. An electronic device, wherein: comprising at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs or instructions; The processor is configured to execute the computer program or instruction so as to enable the electronic device to implement the error location method according to any one of claims 1 to 7.

10. A storage medium, applied to an electronic device, wherein: The storage medium carries one or more computer programs, and the one or more computer programs can be executed by the electronic device, so that the electronic device implements the error location method according to any one of claims 1 to 7.

Images