WO2020233066A1 - 基于数据计算链路的异常处理方法以及相关设备 - Google Patents
基于数据计算链路的异常处理方法以及相关设备 Download PDFInfo
- Publication number
- WO2020233066A1 WO2020233066A1 PCT/CN2019/121692 CN2019121692W WO2020233066A1 WO 2020233066 A1 WO2020233066 A1 WO 2020233066A1 CN 2019121692 W CN2019121692 W CN 2019121692W WO 2020233066 A1 WO2020233066 A1 WO 2020233066A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- transaction
- transaction node
- log
- node
- root cause
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Definitions
- This application relates to the field of data processing technology, and in particular to an abnormal processing method based on a data calculation link and related equipment.
- Transaction behavior is a kind of data calculation (or data settlement) behavior.
- the completion of a transaction usually needs to be completed by multiple teams. For example, when a user purchases a product, the transaction request will pass through Order nodes, cashier nodes, account system nodes, payment channel nodes, and bank nodes, etc., and the nodes involved above are respectively responsible for different R&D teams.
- the transaction request is abnormal, the efficiency of locating the abnormal node and handling the abnormality is low due to the many nodes in the transaction request path.
- This application proposes a technical solution for abnormality processing based on a data calculation link, which can improve the positioning efficiency of abnormal nodes in the data calculation link, especially the transaction link.
- an abnormality processing method based on a data calculation link the data calculation link is specifically a transaction link, and the transaction link includes a plurality of transaction nodes; the method includes: In the case of abnormal transaction invocation on the link, the first transaction node receives the invocation information returned by the second transaction node; the invocation information includes the error codes of N transaction nodes, where N is an integer greater than 0; The transaction node is the uppermost transaction node of the transaction link; the second transaction node is the next transaction node of the first transaction node; the first transaction node obtains the The log information of each of the N transaction nodes; the first transaction node determines the root cause of the abnormal transaction call of the transaction link and the target of the root cause according to the log information of each transaction node Transaction node; the first transaction node indicates the root cause to the target transaction node, so that the target transaction node can repair the link abnormality according to the root cause.
- the log information is standardized log information
- the standardized log information conforms to a log standard format
- the first transaction node determines the transaction link according to the log information of each transaction node
- the root cause of the abnormal transaction call and the target transaction node that caused the root cause specifically include: the first transaction node matches the standardized log information according to a regular expression to determine the first target location of the root cause;
- the first transaction node extracts the root cause of the abnormal transaction call of the transaction link according to the first target location, and determines the target transaction node that causes the root cause according to the root cause.
- the first transaction node can comprehensively and accurately diagnose the root cause of abnormality in the transaction link according to the corresponding log information of each error code, which improves the efficiency of abnormal transaction node location and abnormality handling when an abnormality occurs in the transaction link.
- the first transaction node matches the standardized log information according to a regular expression to determine the first target location of the root cause, including: the first transaction node matches according to the regular expression Each log segment with an error identification in the standardized log information; the content of each log segment is the reason for the occurrence of the error identification; the first transaction node converts all the logs according to the log printing time of each log segment The location of the log segment with the earliest log printing time is determined as the first target location of the root cause.
- the regular expression is used to retrieve text that conforms to a certain pattern (rule).
- regular expressions are used to retrieve log segments with error identifiers.
- the error identifiers can be INFO, WARN, ERROR, FATAL, etc., thereby improving The efficiency of retrieval.
- the solution of determining the location of the root cause according to the log printing time in this embodiment is applicable to a transaction link with only one link.
- the first transaction node matches the standardized log information according to a regular expression to determine the first target location of the root cause, including: the first transaction node matches according to the regular expression Each log segment with an error identifier in the standardized log information; the content of each log segment is the reason for the error identifier; the first transaction node compares all log segments according to the log error level of each log segment The location of the log segment with the highest log error level is determined as the first target location of the root cause.
- Regular expressions are used to retrieve log segments with error identifiers, where the error identifiers can be INFO, WARN, ERROR, FATAL, etc., which improves the efficiency of retrieval.
- the solution of determining the location of the root cause according to the log error level in this embodiment is applicable to the transaction link of the multi-branch link.
- the error code includes an identifier of the transaction node
- the first transaction node obtains log information of each of the N transaction nodes according to the N error codes, including: The first transaction node determines, according to the identifiers of the N transaction nodes included in the N error codes, the N transaction nodes with abnormal transaction call; the first transaction node obtains from the N transaction nodes Log information related to the N error codes.
- the first transaction node can obtain the error code of the abnormal transaction node in its downstream transaction link at one time according to the call information returned by each transaction node, and can quickly locate the abnormal transaction node according to the error code, without requiring one by one. Troubleshoot each node to improve the efficiency of locating abnormal transaction nodes.
- the error codes of the N transaction nodes include the error codes of the second transaction node and the error codes of N-1 other transaction nodes , whereby improving the abnormal location and processing efficiency of the transaction link, avoiding to check each transaction node in the transaction link one by one.
- the error codes of the N transaction nodes have the same data format.
- the use of the same data format facilitates the unified processing of the error code of each transaction node in its downstream transaction link by the upstream transaction node.
- an abnormality processing device for a data calculation link, the data calculation link is a transaction link, and the transaction link includes multiple transaction nodes; the device includes: a receiving unit and an acquiring unit , The determining unit, the indicating unit, the receiving unit is used to receive the call information returned by the second transaction node in the case of a transaction call abnormality in the transaction link; the call information includes the error codes of the N transaction nodes, so The N is an integer greater than 0; the second transaction node is the next transaction node of the first transaction node; the obtaining unit is configured to obtain the N transaction nodes according to the N error codes The log information of each transaction node; the determining unit is used to determine the root cause of the transaction call abnormality of the transaction link and the target transaction node that caused the root cause according to the log information of each transaction node; The indication unit is configured to indicate the root cause to the target transaction node, so that the target transaction node can repair the link abnormality according to the root cause.
- the log information is standardized log information, and the standardized log information conforms to a log standard format.
- the determining unit may further include a matching unit and an extracting unit.
- the matching unit is used to express Formula matching the standardized log information to determine the first target location of the root cause;
- the extraction unit is used to extract the root cause of the abnormal transaction call of the transaction link according to the first target location, and Determine the target transaction node that causes the root cause according to the root cause.
- the matching unit is configured to match each log segment with an error identifier in the standardized log information according to the regular expression; the content of each log segment is the cause of the error identifier ; According to the log print time of each log segment, the location of the log segment with the earliest log print time is determined as the first target location of the root cause.
- the matching unit is further configured to match each log segment with an error identifier in the standardized log information according to the regular expression; the content of each log segment is the content of the error identifier.
- Reason According to the log error level of each log segment, the location of the log segment with the highest log error level is determined as the first target location of the root cause.
- the error code includes the identifier of the transaction node
- the obtaining unit is configured to determine the N transaction call abnormalities that have occurred according to the identifiers of the N transaction nodes included in the N error codes.
- Transaction nodes obtain log information related to the N error codes from the N transaction nodes.
- the error codes of the N transaction nodes include the error codes of the second transaction node and the error codes of N-1 other transaction nodes .
- the error codes of the N transaction nodes have the same data format.
- an electronic device including: a processor; a memory for storing executable instructions of the processor; wherein the processor is configured to call the instructions stored in the memory, The invocation of the instruction causes the processor to execute the method of any one of the embodiments of the first aspect of the present application.
- a computer-readable storage medium may be a non-volatile computer-readable storage medium, such as read-only memory (ROM), flash memory (Flash memory), etc., may also be computer readable storage media, such as random access memory (Random Access Memory, RAM).
- the computer-readable storage medium stores a computer program, and the computer program is executed by a processor in a method according to any one of the embodiments of the first aspect of the present application.
- the first transaction node can obtain the error code of the transaction node that is abnormal in its downstream link at one time according to the returned call information, and then obtain the log information related to the error code, and pass The log information derives the root cause of the abnormal transaction call, and quickly locates the target transaction node that caused the root cause through the root cause, and finally sends the root cause to the target transaction node so that the target transaction node can repair it according to the root cause.
- This solution does not It is necessary to troubleshoot each node one by one.
- the first transaction node can comprehensively and accurately diagnose the root cause of abnormality in the transaction link according to the corresponding log information of each error code, which improves the abnormal transaction when an abnormality occurs in the transaction link. The efficiency of node location and exception handling.
- FIG. 1 is a schematic flowchart of a method for processing a transaction link abnormality provided by an embodiment of the present application
- Figure 2 is a schematic diagram of the interaction of each node in the transaction link provided by an embodiment of the present application
- FIG. 3 is a schematic structural diagram of a transaction link abnormal processing device provided by an embodiment of the present application.
- Fig. 4 is a schematic structural diagram of another transaction link abnormal processing device provided by an embodiment of the present application.
- FIG. 5 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
- the transaction link exception processing method of the present application is suitable for exception processing in the transaction link.
- a transaction processing requires more than two transaction nodes and more than ten or even dozens of transaction calls to complete the transaction.
- each transaction node if there is an abnormality in transaction calls between different transaction nodes, each transaction node generally returns a specific error code defined by itself, and each transaction node can only perceive the abnormality of the downstream transaction node directly called. For example, when a user places an order, the transaction request will pass through the order transaction node, cash register transaction node, account system transaction node, payment channel transaction node, and bank transaction node in turn.
- the account system transaction node can only sense the direct call
- the payment channel transaction node is abnormal, but the bank transaction node that is indirectly called through the payment channel transaction node cannot be sensed.
- the current existing solutions need to troubleshoot the log information of each node one by one.
- the abnormal location and abnormal handling efficiency of the transaction link of multiple transaction nodes can be improved. For details, see the following description.
- FIG. 1 is a schematic flowchart of a method for processing an abnormality of a data calculation link (transaction link) provided by an embodiment of the present application.
- the transaction call exception is thrown when the current transaction node's processing of the transaction message does not conform to the preset processing logic, and the transaction call exception includes system call exceptions and business calls Exceptions, where system call exceptions are abnormalities in which the hardware of the transaction node or operating system fails, and business call exceptions are those caused by calls that do not meet business requirements.
- the first transaction node is the uppermost transaction node in the transaction link, that is, the transaction node that initiates the call earliest, and the second transaction node is the next transaction node connected to the first transaction node.
- the first transaction node receives the invocation information returned by the second transaction node, where the invocation information includes error codes of N transaction nodes, where N is an integer greater than zero.
- the error codes of the N transaction nodes include the error codes of the second transaction node and the error codes of N-1 other transaction nodes.
- FIG. 2 is a schematic diagram of the interaction of each node in the transaction link provided by an embodiment of the present application.
- a transaction link includes: transaction node A, transaction node B, transaction node C, transaction node D, transaction node E, a total of 5 transaction nodes
- the mutual transaction call relationship includes: transaction node A calls transaction node B, Transaction node B calls transaction node C, transaction node C calls transaction node D and transaction node E, transaction node D and transaction node E return a response to transaction node C, transaction node C returns a response to transaction node B, and transaction node B returns a response to Transaction node A.
- the transaction nodes may be logical nodes divided according to logical functions, or physical nodes divided according to actual physical service nodes, which are not specifically limited in this application.
- the invocation information may include: whether the transaction invocation service is processed successfully, and, in the case of a transaction invocation processing exception, the invocation information includes error context, errors of the N transaction nodes The code is recorded in the error context.
- the error code stack mode can be used for recording
- the error code queue mode can also be used for recording
- other data structures can be used for recording.
- transaction node C after transaction node C generates the error code of transaction node C, if transaction node C has received the error context in the call information fed back by transaction node E, and the error context has been recorded The error code of transaction node E, transaction node C can add the error code of transaction node C to the error context, so that the error code of transaction node C and the error code of transaction node E are recorded in the error context.
- the current transaction node can create a new error context and record the error code of the system at the new level. In the wrong context. For example, when a transaction call exception occurs, transaction node E can generate an error code of transaction node E, create a new error context, record the error code of transaction node E in the error context, and feed it back to transaction node C.
- the upper-level transaction node can obtain the error code of the transaction node that is abnormal in its downstream transaction link at one time according to the returned call information, and the abnormality can be quickly located according to the error code There is no need to troubleshoot each node one by one, which improves the efficiency of locating abnormal transaction nodes.
- the error codes generated by different transaction nodes have the same data format.
- the error code of transaction node C generated at transaction node C and the error code of transaction node E generated at transaction node E have the same data format.
- the error codes generated by different transaction nodes all adopt the TLV (Tag-Length-Value) data format.
- TLV is an abbreviation of Tag, Length, and Value.
- a basic data element includes the above three fields.
- Tag uniquely identifies the data element, Length is the length of the Value field, and Value is the data itself.
- TLV data format is conducive to the expansion of error code content. See Table 1 for details. Table 1 is an example of the error code data format.
- digits 1 to 5 represent the error level.
- the error level can be divided into 4 different error levels, the error level from low to high is: INFO, WARN, ERROR, FATAL.
- INFO-level log information is used to output some important information about program operation in the production environment
- WARN-level log information is used to warn potential errors
- ERROR-level log information indicates that although an error event occurs, it still does not affect the continued operation of the system.
- the FATAL level log information records serious error events, and the error time will cause the application to crash.
- Digits 6 to 11 represent the transaction node number, which uniquely identifies the transaction node.
- each transaction node is assigned a transaction node number in advance to uniquely identify the transaction node, and a specific transaction node can be directly located through an error code according to this identification.
- the transaction node number can also be represented by the IP (Internet Protocol) address of the transaction node or the domain name of the transaction node. The embodiment of the application does not specifically limit the transaction node number.
- Bits 12 to 18 represent the error code, which is a self-defined error code within each transaction node, such as the custom error shown in Table 2.
- Illegal request parameter 1001 User authentication failed 1002
- Illegal authorization information 1003 Application is not authorized 1004
- Information is invalid or out of range 1006
- the update token provided has expired 1007
- the field does not match the one filled in when registering the app 1008
- the error code data format is only an example, the error code may include more data content, or may be a fixed format other than the TLV format, which is not limited in this application.
- the embodiment of this application requires that the data format of the error codes used by the transaction nodes of each layer is the same. The purpose is to use the same data format to facilitate the upstream transaction node's error code for each transaction node in the downstream transaction link Perform unified processing.
- the first transaction node obtains log information of each of the N transaction nodes according to the N error codes.
- the error code includes the identifier of the transaction node, and the first transaction node determines the N transaction call abnormalities based on the identifiers of the N transaction nodes included in the N error codes.
- Transaction node where the identifier may be the domain name or Internet Protocol address of the transaction node; the first transaction node obtains log information related to the N error codes from the N transaction nodes, which is specifically implemented as :
- the first transaction node sends respective error codes to the N transaction nodes, and after receiving the respective error codes, the N transaction nodes query log information according to the respective error codes
- the library obtains the log information related to the respective error codes, and then sends the log information related to the respective error codes to the first transaction node.
- the first transaction node determines the root cause of the abnormal transaction call of the transaction link and the target transaction node that caused the root cause according to the log information of each transaction node.
- the log information is standardized log information, and the standardized log information conforms to the log standard format.
- Step 103 can be implemented in the following manner: the first transaction node matches the standardized log information according to a regular expression. Log information to determine the first target location of the root cause; the first transaction node extracts the root cause of the abnormal transaction call of the transaction link according to the first target location, and determines the cause based on the root cause The target transaction node of the root cause. In this solution, the first transaction node determines the first target location of the root cause according to the regular expression matching standardized log information.
- This application provides two implementation methods. For details, refer to the following description.
- the first transaction node matches each log segment with an error identifier in the standardized log information according to a regular expression; wherein the content of each log segment is the reason for the error identifier; the first transaction node matches the log segment according to the
- the log printing time determines the location of the log segment with the earliest log printing time as the first target location of the root cause.
- the regular expression is usually used to retrieve text that conforms to a certain pattern (rule).
- regular expressions are used to retrieve log segments with error identifiers.
- the error identifiers can be INFO, WARN, ERROR, FATAL, etc.
- the root cause location can be obtained according to the log print time of each log segment, that is, the log segment with the earliest log print time is used as the root cause location.
- the location of the root cause based on the log printing time is suitable for a transaction link with only one link.
- the first transaction node matches each log segment with an error identifier in the standardized log information according to the regular expression; the content of each log segment is the reason for the error identifier; the first transaction node matches the log segment according to the
- the log error level determines the location of the log segment with the highest log error level as the first target location of the root cause.
- the regular expression is usually used to retrieve text that conforms to a certain pattern (rule).
- regular expressions are used to retrieve log segments with error identifiers.
- the error identifiers can be INFO, WARN, ERROR, FATAL, etc.
- the root cause location can be obtained according to the log error level of each log segment, that is, the log segment with the highest log error level is used as the root cause location.
- the location of the root cause determined according to the log error level is applicable to the transaction link of the multi-branch link.
- the first transaction node indicates the root cause to the target transaction node, so that the target transaction node can repair the link abnormality according to the root cause.
- transaction node B can only determine through the error code that the exception is caused by the absence of the memory space pointed to by the pointer.
- transaction node B cannot determine the The abnormality is caused by the processing logic of its own transaction node conforming to the preset logic, or the processing logic of its downstream transaction node does not conform to the preset logic. Therefore, transaction node A needs to perform step S101-step S103 to obtain the root cause of the null pointer abnormality.
- the root cause of the null pointer abnormality obtained by transaction node A is that transaction node E has not uploaded the specified file, and then transaction node A Send the root cause of the null pointer exception to the transaction node E, and the transaction node E can repair the link exception based on the root cause sent by the transaction node A.
- the abnormal location and abnormal handling efficiency of the transaction link are improved, and it is avoided to check each transaction node in the transaction link one by one.
- the first transaction node can obtain the error code of the transaction node that is abnormal in its downstream link at one time according to the returned call information, and then obtain the log information related to the error code, and obtain the log information from the log information
- the root cause of the abnormal transaction call and quickly locate the target transaction node that caused the root cause through the root cause, and finally send the root cause to the target transaction node, so that the target transaction node can repair according to the root cause.
- the node eliminates the problem.
- the first transaction node can comprehensively and accurately diagnose the root cause of the abnormality in the transaction link according to the corresponding log information of each error code, which improves the location and abnormality of the abnormal transaction node when an abnormality occurs in the transaction link. Processing efficiency.
- FIG. 3 is a schematic structural diagram of a transaction link exception processing apparatus provided by an embodiment of the present application.
- the device is applied to a transaction link, and the transaction link includes a plurality of transaction nodes; the device 300 includes: a receiving unit 301, an obtaining unit 302, a determining unit 303, and an indicating unit 304.
- the receiving unit 301 is used for receiving the calling information returned by the second transaction node by the first transaction node in the case of abnormal transaction invocation on the transaction link;
- the invocation information includes the error codes of N transaction nodes, and the N Is an integer greater than 0;
- the second transaction node is the next transaction node of the first transaction node;
- the obtaining unit 302 is configured to obtain the log information of each of the N transaction nodes by the first transaction node according to the N error codes;
- the determining unit 303 is configured to determine the root cause of the abnormal transaction call of the transaction link and the target transaction node that caused the root cause by the first transaction node according to the log information of each transaction node;
- the indicating unit 304 is configured to indicate the root cause to the target transaction node by the first transaction node, so that the target transaction node can repair the link abnormality according to the root cause.
- the log information is standardized log information, and the standardized log information conforms to a log standard format.
- the determining unit 303 includes a matching unit 401, an extracting unit 402, and the matching unit 401 Used to match the standardized log information according to a regular expression to determine the first target location of the root cause; the extracting unit 402 is used to extract the transaction of the transaction link according to the first target location Call the root cause of the abnormality, and determine the target transaction node that caused the root cause according to the root cause.
- the matching unit 401 is configured to match each log segment with an error identifier in the standardized log information according to the regular expression; the content of each log segment is the content of the error identifier.
- Reason According to the log print time of each log segment, the location of the log segment with the earliest log print time is determined as the first target location of the root cause.
- the matching unit 401 is further configured to match each log segment with an error identifier in the standardized log information according to the regular expression; the content of each log segment is the occurrence of the error identifier The reason; according to the log error level of each log segment, the location of the log segment with the highest log error level is determined as the first target location of the root cause.
- the error code includes the identifier of the transaction node
- the acquiring unit 302 is configured to determine, according to the identifiers of the N transaction nodes included in the N error codes, that an abnormal transaction call occurs N transaction nodes; obtain log information related to the N error codes from the N transaction nodes.
- the error codes of the N transaction nodes include the error codes of the second transaction node and the error codes of N-1 other transaction nodes .
- the error codes of the N transaction nodes have the same data format.
- the functions or modules contained in the apparatus provided in the embodiments of the application can be used to execute the methods described in the above method embodiments.
- the functions or modules contained in the apparatus provided in the embodiments of the application can be used to execute the methods described in the above method embodiments.
- An embodiment of the present application further provides an electronic device, including: a memory, configured to store executable instructions; and a processor, configured to communicate with the memory to execute the executable instructions, thereby completing any of the foregoing embodiments of the present application. Describes the operation of the transaction link exception handling method.
- FIG. 5 is a structural block diagram of an electronic device provided by an embodiment of the present application.
- the electronic device includes: one or more processors 501; one or more input interfaces 502, one or more output interfaces 503, and a memory 504.
- the aforementioned processor 501, input interface 502, output interface 503, and memory 504 are connected via a bus 505.
- the memory 502 is used to store instructions
- the processor 501 is used to execute instructions stored in the memory 502.
- the processor 501 is configured to call the program instructions to execute:
- the call information returned by the second transaction node is received through the input interface 502;
- the call information includes the error codes of N transaction nodes, where N is an integer greater than 0;
- the first transaction node is the uppermost transaction node of the transaction link;
- the second transaction node is the next transaction node of the first transaction node;
- the first transaction node obtains log information of each of the N transaction nodes through the input interface 502 according to the N error codes;
- the first transaction node determines the root cause of the abnormal transaction call of the transaction link and the target transaction node that caused the root cause according to the log information of each transaction node;
- the root cause is indicated to the target transaction node, so that the target transaction node can repair the link abnormality according to the root cause.
- the processor 501 may be a central processing unit (Central Processing Unit, CPU), and the processor may also be other general-purpose processors or digital signal processors (DSP). , Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
- the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
- the memory 504 may include a read-only memory and a random access memory, and provides instructions and data to the processor 501. A part of the memory 504 may also include a non-volatile random access memory. For example, the memory 504 may also store device type information.
- the processor 501 is used to execute the transaction link abnormal processing method described in the embodiments of the present application
- the input interface 502 is used to receive data
- the output interface 503 is used to output data.
- the processor 501, the input interface 502, and the output interface 503 can execute the implementation manners described in the various embodiments of the transaction link exception handling method provided in the embodiments of the present application. For brevity, details are not repeated here.
- a computer-readable storage medium stores a computer program, the computer program includes program instructions, and the program instructions are implemented when executed by a processor:
- the first transaction node receives the call information returned by the second transaction node;
- the call information includes the error codes of N transaction nodes, where N is an integer greater than 0;
- a transaction node is the uppermost transaction node of the transaction link;
- the second transaction node is the next transaction node of the first transaction node;
- the first transaction node obtains the transaction node according to the N error codes
- the first transaction node determines, according to the log information of each transaction node, the root cause of the abnormal transaction call of the transaction link and the root cause Target transaction node;
- the first transaction node indicates the root cause to the target transaction node, so that the target transaction node can repair the link abnormality according to the root cause.
- the computer-readable storage medium may be an internal storage unit of the electronic device described in any of the foregoing embodiments, such as a hard disk or memory of a terminal.
- the computer-readable storage medium may also be an external storage device of the terminal, such as a plug-in hard disk equipped on the terminal, a Smart Media Card (SMC), or a Secure Digital (SD) card , Flash Card, etc.
- the computer-readable storage medium may also include both an internal storage unit of the electronic device and an external storage device.
- the computer-readable storage medium is used to store the computer program and other programs and data required by the electronic device.
- the computer-readable storage medium can also be used to temporarily store data that has been output or will be output.
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
错误码 | 错误描述 |
1000 | 非法的请求参数 |
1001 | 用户认证失败 |
1002 | 非法的授权信息 |
1003 | 应用没有被授权 |
1004 | 字段超过定义范围 |
1005 | 信息无效或超出范围 |
1006 | 提供的更新令牌已过期 |
1007 | 字段与注册应用时所填写的不匹配 |
1008 | 服务器拒绝授予数据访问权限 |
Claims (20)
- 一种基于数据计算链路的异常处理方法,其特征在于,所述数据计算链路为交易链路,所述交易链路包括多个交易节点;所述方法包括:在交易链路出现交易调用异常的情况下,第一交易节点接收第二交易节点返回的调用信息;所述调用信息包括N个交易节点的错误码,所述N为大于0的整数;所述第一交易节点为所述交易链路的最上层交易节点;所述第二交易节点为所述第一交易节点的下一交易节点;所述第一交易节点根据N个所述错误码,获取所述N个交易节点中的各个交易节点的日志信息;所述第一交易节点根据所述各个交易节点的日志信息,确定所述交易链路的交易调用异常的根因以及导致所述根因的目标交易节点;所述第一交易节点向所述目标交易节点指示所述根因,以便于所述目标交易节点根据所述根因进行链路异常的修复。
- 根据权利要求1所述的方法,其特征在于,所述日志信息为标准化的日志信息,所述标准化的日志信息符合日志标准格式,所述第一交易节点根据所述各个交易节点的日志信息,确定所述交易链路的交易调用异常的根因以及导致所述根因的目标交易节点,具体包括:所述第一交易节点根据正则表达式匹配所述标准化的日志信息,确定所述根因的第一目标位置;所述第一交易节点根据所述第一目标位置,提取所述交易链路的交易调用异常的根因,并根据所述根因确定导致所述根因的目标交易节点。
- 根据权利要求2所述的方法,其特征在于,所述第一交易节点根据正则表达式匹配所述标准化的日志信息,确定所述根因的第一目标位置,包括:所述第一交易节点根据所述正则表达式匹配所述标准化的日志信息中出现错误标识的各个日志段;所述各个日志段的内容为发生所述错误标识的原因;所述第一交易节点根据所述各个日志段的日志打印时间,将所述日志打印时间最早的日志段的所在位置,确定为所述根因的第一目标位置。
- 根据权利要求2所述的方法,其特征在于,所述第一交易节点根据正则表达式匹配所述标准化的日志信息,确定所述根因的第一目标位置,包括:所述第一交易节点根据所述正则表达式匹配所述标准化的日志信息中出现错误标识的各个日志段;所述各个日志段的内容为发生所述错误标识的原因;所述第一交易节点根据所述各个日志段的日志错误等级,将所述日志错误等级最高的日志段的所在位置,确定为所述根因的第一目标位置。
- 根据权利要求1所述的方法,其特征在于,所述错误码包括所述交易节点的标识,所述第一交易节点根据N个所述错误码,获取所述N个交易节点中的各个交易节点的日志信息,包括:所述第一交易节点根据所述N个所述错误码包括的N个交易节点的标识,确定出现交易调用异常的N个交易节点;所述第一交易节点向所述N个交易节点,获取与N个所述错误码相关的日志信息。
- 根据权利要求1所述的方法,其特征在于,在第二交易节点也出现交易调用异常的情况下,所述N个交易节点的错误码包括所述第二交易节点的错误码以及N-1个其他交易节点的错误码。
- 根据权利要求1-6任一项所述的方法,其特征在于,所述N个交易节点的错误码具有相同的数据格式。
- 根据权利要求7所述的方法,其特征在于,所述交易调用异常包括系统调用异常和业务调用异常,所述系统调用异常表示交易节点的硬件出现故障或操作系统出现故障导致的异常,所述业务调用异常表示交易节点的调用不满足业务需求导致的异常。
- 一种数据计算链路的异常处理装置,其特征在于,所述数据计算链路为交易链路,所述交易链路包括多个交易节点;所述装置包括:接收单元,获取单元,确定单元,指示单元,所述接收单元用于,在交易链路出现交易调用异常的情况下,接收第二交易节点返回的调用信息;所述调用信息包括N个交易节点的错误码,所述N为大于0的整数;所述第二交易节点为所述第一交易节点的下一交易节点;所述获取单元用于,根据N个所述错误码,获取所述N个交易节点中的各个交易节点的日志信息;所述确定单元用于,根据所述各个交易节点的日志信息,确定所述交易链路的交易调用异常的根因以及导致所述根因的目标交易节点;所述指示单元用于,向所述目标交易节点指示所述根因,以便于所述目标交易节点根据所述根因进行链路异常的修复。
- 根据权利要求9所述的装置,其特征在于,所述日志信息为标准化的日志信息,所述标准化的日志信息符合日志标准格式;所述确定单元进一步包括匹配单元和提取单元;所述匹配单元具体用于,根据正则表达式匹配所述标准化的日志信息,确定所述根因的第一目标位置;所述提取单元具体用于,根据所述第一目标位置,提取所述交易链路的交易调用异常的根因,并根据所述根因确定导致所述根因的目标交易节点。
- 根据权利要求10所述的装置,其特征在于,所述匹配单元具体用于,根据所述正则表达式匹配所述标准化的日志信息中出现错误标识的各个日志段;所述各个日志段的内容为发生所述错误标识的原因;根据所述各个日志段的日志打印时间,将所述日志打印时间最早的日志段的所在位置,确定为所述根因的第一目标位置。
- 根据权利要求10所述的装置,其特征在于,所述匹配单元具体用于:根据所述正则表达式匹配所述标准化的日志信息中出现错误标识的各个日志段;所述各个日志段的内容为发生所述错误标识的原因;根据所述各个日志段的日志错误等级,将所述日志错误等级最高的日志段的所在位置,确定为所述根因的第一目标位置。
- 根据权利要求9所述的装置,其特征在于,所述错误码包括所述交易节点的标识;所述获取单元具体用于:根据所述N个所述错误码包括的N个交易节点的标识,确定出现交易调用异常的N个交易节点;向所述N个交易节点,获取与N个所述错误码相关的日志信息。
- 根据权利要求9所述的装置,其特征在于,在第二交易节点也出现交易调用异常的情况下,所述N个交易节点的错误码包括所述第二交易节点的错误码以及N-1个其他交易节点的错误码。
- 一种电子设备,其特征在于,包括:处理器;用于存储处理器可执行指令的存储器;其中,所述处理器被配置为调用所述存储器存储的指令,对所述指令的调用使得所述处理器执行以下步骤:在交易链路出现交易调用异常的情况下,第一交易节点接收第二交易节点返回的调用信息;所述调用信息包括N个交易节点的错误码,所述N为大于0的整数;所述第一交易节点为所述交易链路的最上层交易节点;所述第二交易节点为所述第一交易节点的下一交易节点;所述第一交易节点根据N个所述错误码,获取所述N个交易节点中的各个交易节点的日志信息;所述第一交易节点根据所述各个交易节点的日志信息,确定所述交易链路的交易调用异常的根因以及导致所述根因的目标交易节点;所述第一交易节点向所述目标交易节点指示所述根因,以便于所述目标交易节点根据所述根因进行链路异常的修复。
- 根据权利要求15所述的电子设备,其特征在于,所述日志信息为标准化的日志信息,所述标准化的日志信息符合日志标准格式;当所述指令被所述处理器执行时,使得所述处理器具体执行以下步骤:根据正则表达式匹配所述标准化的日志信息,确定所述根因的第一目标位置;根据所述第一目标位置,提取所述交易链路的交易调用异常的根因,并根据所述根因确定导致所述根因的目标交易节点。
- 根据权利要求16所述的电子设备,其特征在于,当所述指令被所述处理器执行时,使得所述处理器具体执行以下步骤:根据所述正则表达式匹配所述标准化的日志信息中出现错误标识的各个日志段;所述各个日志段的内容为发生所述错误标识的原因;根据所述各个日志段的日志打印时间,将所述日志打印时间最早的日志段的所在位置,确定为所述根因的第一目标位置。
- 根据权利要求16所述的电子设备,其特征在于,当所述指令被所述处理器执行时,使得所述处理器具体执行以下步骤:根据所述正则表达式匹配所述标准化的日志信息中出现错误标识的各个日志段;所述各个日志段的内容为发生所述错误标识的原因;根据所述各个日志段的日志错误等级,将所述日志错误等级最高的日志段的所在位置,确定为所述根因的第一目标位置。
- 根据权利要求15所述的电子设备,其特征在于,所述错误码包括所述交易节点的标识;当所述指令被所述处理器执行时,使得所述处理器具体执行以下步骤:根据所述N个所述错误码包括的N个交易节点的标识,确定出现交易调用异常的N个交易节点;向所述N个交易节点,获取与N个所述错误码相关的日志信息。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质存储有计算机程序,所述计算机程序被处理器执行以实现权利要求1至7任意一项所述的方法。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910420339.XA CN110223173A (zh) | 2019-05-20 | 2019-05-20 | 交易链路异常处理方法以及相关设备 |
CN201910420339.X | 2019-05-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020233066A1 true WO2020233066A1 (zh) | 2020-11-26 |
Family
ID=67821501
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/121692 WO2020233066A1 (zh) | 2019-05-20 | 2019-11-28 | 基于数据计算链路的异常处理方法以及相关设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110223173A (zh) |
WO (1) | WO2020233066A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112948207A (zh) * | 2021-02-23 | 2021-06-11 | 中国工商银行股份有限公司 | 信息传递方法、装置、电子设备和介质 |
US11489717B2 (en) | 2020-07-08 | 2022-11-01 | Alipay (Hangzhou) Information Technology Co., Ltd. | Method, apparatus, and electronic device for transaction link exception handling |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110223173A (zh) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | 交易链路异常处理方法以及相关设备 |
CN113407370A (zh) * | 2020-03-16 | 2021-09-17 | 中国移动通信有限公司研究院 | 根因错误的聚类方法、装置、设备及计算机可读存储介质 |
CN112487071A (zh) * | 2020-11-17 | 2021-03-12 | 中信银行股份有限公司 | 一种交易查询方法、装置、电子设备及可读存储介质 |
CN113220540B (zh) * | 2021-06-07 | 2023-04-25 | 深圳华锐分布式技术股份有限公司 | 业务管理方法、装置、计算机设备和存储介质 |
WO2023277802A2 (en) * | 2021-07-01 | 2023-01-05 | Shopee Singapore Private Limited | Device and method for identifying errors in a software application |
CN113778804A (zh) * | 2021-09-15 | 2021-12-10 | 北京有竹居网络技术有限公司 | 一种日志打印方法、装置、计算机设备及存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101309525A (zh) * | 2008-06-30 | 2008-11-19 | 中兴通讯股份有限公司 | 一种自动交换光网络中依据故障定位的路由恢复方法 |
US20110205909A1 (en) * | 2008-10-23 | 2011-08-25 | Huawei Technologies Co., Ltd. | Method, node and system for obtaining link aggregation group information |
CN107992415A (zh) * | 2017-11-28 | 2018-05-04 | 中国银联股份有限公司 | 一种交易系统的故障定位和分析方法及相关服务器 |
CN109308252A (zh) * | 2017-07-27 | 2019-02-05 | 中国移动通信集团浙江有限公司 | 一种故障定位处理方法及装置 |
CN110223173A (zh) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | 交易链路异常处理方法以及相关设备 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108933695B (zh) * | 2018-06-25 | 2021-05-25 | 百度在线网络技术(北京)有限公司 | 用于处理信息的方法和装置 |
CN109766323A (zh) * | 2018-12-17 | 2019-05-17 | 深圳壹账通智能科技有限公司 | 贷款交易全链路监控方法、装置、计算机设备和存储介质 |
-
2019
- 2019-05-20 CN CN201910420339.XA patent/CN110223173A/zh active Pending
- 2019-11-28 WO PCT/CN2019/121692 patent/WO2020233066A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101309525A (zh) * | 2008-06-30 | 2008-11-19 | 中兴通讯股份有限公司 | 一种自动交换光网络中依据故障定位的路由恢复方法 |
US20110205909A1 (en) * | 2008-10-23 | 2011-08-25 | Huawei Technologies Co., Ltd. | Method, node and system for obtaining link aggregation group information |
CN109308252A (zh) * | 2017-07-27 | 2019-02-05 | 中国移动通信集团浙江有限公司 | 一种故障定位处理方法及装置 |
CN107992415A (zh) * | 2017-11-28 | 2018-05-04 | 中国银联股份有限公司 | 一种交易系统的故障定位和分析方法及相关服务器 |
CN110223173A (zh) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | 交易链路异常处理方法以及相关设备 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11489717B2 (en) | 2020-07-08 | 2022-11-01 | Alipay (Hangzhou) Information Technology Co., Ltd. | Method, apparatus, and electronic device for transaction link exception handling |
CN112948207A (zh) * | 2021-02-23 | 2021-06-11 | 中国工商银行股份有限公司 | 信息传递方法、装置、电子设备和介质 |
Also Published As
Publication number | Publication date |
---|---|
CN110223173A (zh) | 2019-09-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020233066A1 (zh) | 基于数据计算链路的异常处理方法以及相关设备 | |
EP3373516B1 (en) | Method and device for processing service calling information | |
CN110245154B (zh) | 多路链接异常处理方法以及相关设备 | |
CN104718533B (zh) | 企业设备的硬件故障管理系统、方法及架构 | |
CN107633016B (zh) | 数据处理方法及装置和电子设备 | |
CN110601880B (zh) | 一种云平台、业务处理方法、命令接口及计算机设备 | |
WO2019019640A1 (zh) | 订单信息的模拟处理方法、装置、存储介质和计算机设备 | |
US20210383371A1 (en) | Method of recording transactions based on blockchain and electronic device using the same | |
CN110633977A (zh) | 支付异常处理方法、装置及终端设备 | |
WO2021114627A1 (zh) | 基于分布式事务的数据处理方法、装置、终端及存储介质 | |
CN111651442A (zh) | 一种数据报送方法、装置、电子设备及存储介质 | |
US11816163B2 (en) | Systems and methods for improved transactional mainframes | |
US20140317066A1 (en) | Method of analysing data | |
CN112866285B (zh) | 网关拦截方法、装置、电子设备及存储介质 | |
US11182375B2 (en) | Metadata validation tool | |
US10657120B2 (en) | Cross-platform digital data movement control utility and method of use thereof | |
CN112416784A (zh) | 基于配置中心的接口校验方法、系统及装置及存储介质 | |
CN111367776A (zh) | 资源转移业务的记录方法、装置、设备及存储介质 | |
JP2005242988A (ja) | ログ情報管理システム、サービス提供システム、ログ情報管理プログラムおよびサービス提供プログラム、並びにログ情報管理方法およびサービス提供方法 | |
CN115543837A (zh) | 软件测试方法、装置、电子设备及存储介质 | |
JP2019020864A (ja) | 演算装置 | |
CN111475400A (zh) | 一种业务平台的验证方法及相关设备 | |
CN110648219B (zh) | 一种银行交易系统标准化输入区的方法和装置 | |
US20200174875A1 (en) | Secure forking of error telemetry data to independent processing units | |
CN112035890B (zh) | 一种数据完整性验证方法及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19929983 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19929983 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 18.03.2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 19929983 Country of ref document: EP Kind code of ref document: A1 |