Data management method and device, computer equipment, storage medium and product

Abstract

The invention relates to the technical field of computers, and discloses a data management method and device, computer equipment, a storage medium and a product, and the method comprises the following steps: responding to a configuration operation on a configuration page, generating a configuration data packet, sending the configuration data packet to a server, receiving abnormal data of a target service sent by the server, wherein the server side is used for collecting abnormal information of the target service after the target service is abnormal, and displaying abnormal data on an abnormal data display page of the client side. According to the method provided by the invention, the error description information related to the error code is configured in a configuration mode, so that the error information is quickly modified without being online. By displaying the collected abnormal data on the abnormal data display page, errors can be conveniently inquired according to actual requirements, and the error code management efficiency and the target service detection efficiency are improved.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to data management methods, devices, computer equipment, storage media and products. Background Art

[0002] In a microservice architecture, services communicate through interfaces. When a service calls another service, an error may occur. In order to uniformly manage and handle error situations, a microservice architecture usually defines a set of error codes to indicate error situations. In related technologies, the lack of uniformity in the specification of error codes will increase the cost of abnormal maintenance and processing, affecting the accuracy of detection indicators. Summary of the invention

[0003] In view of this, the present disclosure provides a data management method, apparatus, computer equipment, storage medium and product to solve the problem of low system maintenance efficiency caused by abnormal situation management.

[0004] In a first aspect, the present disclosure provides a data management method, applied to a client, the method comprising:

[0005] In response to a configuration operation on a configuration page, a configuration data packet is generated and sent to a server, wherein the configuration data packet is used to characterize a correspondence between a first error code and first error description information; abnormal data of a target service sent by the server is received, wherein the server is used to collect abnormal information of the target service after the target service is abnormal, wherein the abnormal information includes a second error code, and the abnormal data is obtained based on the second error code and the configuration data packet; and the abnormal data is displayed on an abnormal data display page.

[0006] The data management method provided in this embodiment generates a configuration data packet in response to the configuration operation on the configuration page, sends the configuration data packet to the server, and receives the abnormal data of the target service sent by the server, wherein the server is used to collect the abnormal information of the target service after the target service is abnormal, and displays the abnormal data on the abnormal data display page of the client. The method provided in the embodiment of the present disclosure configures the error description information related to the error code in a configured manner, so as to realize the rapid modification of the error information without going online. By displaying the collected abnormal data on the abnormal data display page, it is convenient to query errors according to actual needs, and improve the management efficiency of error codes and the detection efficiency of target services.

[0007] In a second aspect, the present disclosure provides a data management method, which is applied to a server, and the method includes:

[0008] Receive a configuration data packet sent by a client, wherein the configuration data packet is used to characterize the correspondence between a first error code and first error description information; collect abnormal information of the target service after an abnormality occurs in the target service, wherein the abnormal information includes a second error code; determine abnormal data of the target service based on the second error code and the configuration data packet; and send the abnormal data to the client so as to display the abnormal data on an abnormal data display page of the client.

[0009] In a third aspect, the present disclosure provides a data management device, the device comprising:

[0010] A data packet generation module is used to generate a configuration data packet in response to a configuration operation on a configuration page, and send the configuration data packet to a server, wherein the configuration data packet is used to characterize the correspondence between a first error code and a first error description information; a data receiving module is used to receive abnormal data of a target service sent by the server, wherein the server is used to collect abnormal information of the target service after the target service is abnormal, wherein the abnormal information includes a second error code, and the abnormal data is obtained based on the second error code and the configuration data packet; a data display module is used to display the abnormal data on an abnormal data display page.

[0011] In a fourth aspect, the present disclosure provides a data management device, the device comprising:

[0012] A data packet receiving module is used to receive a configuration data packet sent by a client, wherein the configuration data packet is used to characterize the correspondence between a first error code and a first error description information; an information collection module is used to collect abnormal information of the target service after the target service is abnormal, wherein the abnormal information includes a second error code; a data determination module is used to determine abnormal data of the target service based on the second error code and the configuration data packet; an abnormal data sending module is used to send the abnormal data to the client so that the abnormal data is displayed on the abnormal data display page of the client.

[0013] In a fifth aspect, the present disclosure provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the method of the first aspect or any corresponding embodiment thereof, the second aspect or any corresponding embodiment thereof by executing the computer instructions.

[0014] In a sixth aspect, the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method of the first aspect or any corresponding embodiment thereof, the second aspect or any corresponding embodiment thereof.

[0015] In a seventh aspect, the present disclosure provides a computer program product, comprising computer instructions for causing a computer to execute the method of the first aspect or any corresponding embodiment thereof, the second aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] Figure 1 is a flowchart of a data management method according to an embodiment of the present disclosure;

[0018] Figure 2 is a schematic diagram of an error code details page according to an embodiment of the present disclosure;

[0019] Figure 3 is a scenario schematic diagram of a data management method according to an embodiment of the present disclosure;

[0020] Figure 4 is a schematic diagram of a configuration page according to an embodiment of the present disclosure;

[0021] Figure 5 is a schematic diagram of an error code adding page according to an embodiment of the present disclosure;

[0022] Figure 6 is a schematic diagram of an error code list page according to an embodiment of the present disclosure;

[0023] Figure 7 is a schematic diagram of a downstream error code mapping editing page according to an embodiment of the present disclosure;

[0024] Figure 8 is a schematic diagram of a current service error code mapping editing page according to an embodiment of the present disclosure;

[0025] Fig. 9 is a schematic diagram of a configuration mapping page 1 according to an embodiment of the present disclosure;

[0026] Fig.10 is a schematic diagram of configuration mapping page 2 according to an embodiment of the present disclosure;

[0027] Fig.11 is a schematic diagram of a configuration marking page according to an embodiment of the present disclosure;

[0028] Fig.12 is a schematic diagram of data storage according to an embodiment of the present disclosure;

[0029] Fig.13 is a flowchart of another data management method according to an embodiment of the present disclosure;

[0030] Fig.14 is a schematic diagram of the architecture of a data management system according to an embodiment of the present disclosure;

[0031] Fig.15 is a schematic diagram of mapping between services according to an embodiment of the present disclosure;

[0032] Fig.16 is a structural block diagram of a data management device according to an embodiment of the present disclosure;

[0033] Fig.17 is a structural block diagram of another data management device according to an embodiment of the present disclosure;

[0034] Fig.18 It is a schematic diagram of the hardware structure of the computer device of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present disclosure.

[0036] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0037] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

[0038] As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0039] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet the relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0040] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0041] Error codes are numbers or strings used to identify and describe errors or abnormal situations in computer programs and systems. They provide a unified way to represent errors and avoid the ambiguity and ambiguity that may occur when natural language is used to describe errors. When a service calls a downstream service, it is difficult to distinguish the downstream error code and error information from the error code of this service. When error code specifications are not unified, it will lead to maintenance difficulties and it will be difficult to perceive the possible errors of the downstream services of the service in advance and to carry out corresponding processing and monitoring in a targeted manner.

[0042] Based on this, the embodiment of the present disclosure provides a data management system, including a client and a server. The client is an error code platform that can configure and manage error codes; the server is deployed on the interface of the microservice in the form of an SDK (Software Development Kit). The server is used to detect abnormal conditions of the service and report abnormal data to the error code platform for management. Optionally, a section is made on the RPC (Remote Procedure Call) interface of the microservice in a sectioning manner to detect possible abnormal conditions when the interface of the microservice is called. The data management method is implemented through the data management system. The client and server that implement the above method can be deployed on a desktop terminal or a mobile terminal. The mobile terminal can be at least one of a mobile phone, a tablet computer, a laptop computer, etc.

[0043] According to an embodiment of the present disclosure, a data management method embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0044] In this embodiment, a data management method is provided, which is applied to a client. Figure 1 is a flow chart of a data management method according to an embodiment of the present disclosure, such as Figure 1 As shown, the process includes the following steps:

[0045] Step S101, in response to a configuration operation on a configuration page, a configuration data packet is generated and sent to a server.

[0046] The configuration data packet is used to characterize the corresponding relationship between the first error code and the first error description information.

[0047] This embodiment is used for an error code platform, which is deployed on a client. The configuration page is a display page of the error code platform. There are multiple controls on the configuration page. By interacting with different controls on the configuration page, you can jump from the configuration page to other configuration pages to configure the error code. The first error description information may include error information, error information templates, services, etc. corresponding to the error code. Among them, the error information template is template information containing placeholders, and the corresponding error information can be generated by filling the template information according to the error information when an exception occurs in the preset service. The first error description information may include not only error code related information of the preset service, but also error code related information of the downstream services of the preset service.

[0048] Specifically, the configuration data packet may include the mapping relationship between the error code and error information of the preset service itself, the mapping relationship between the error code and error information of the downstream service of the preset service, the mapping relationship between the error code of the downstream service and the error code of the preset service, etc.

[0049] Through the configuration operation on the client, a configuration data packet is generated, which may include the correspondence between the error codes and error description information of multiple services. The configuration data packet is sent to the server. Specifically, the SDK of the server pulls the configuration data packet from the error code platform, and the SDK stores the configuration data packet on the server.

[0050] Step S102, receiving abnormal data of the target service sent by the server.

[0051] The server is used to collect abnormal information of the target service after the target service is abnormal, and the abnormal information includes a second error code, and the abnormal data is obtained based on the second error code and the configuration data packet.

[0052] The exception information includes the specific error description actually reported by the service during the actual operation process and the second error code corresponding to the error description. The server obtains the error information template corresponding to the second error code from the configuration data packet, and then fills the error information template based on the error information, and can generate the error information corresponding to the second error code. The exception data may include the second error code and the error information corresponding to the second error code. The exception data may also specifically include the time when the error occurred, the source of the error, etc. The server reports the exception data to the client, and may specifically adopt a regular reporting method (for example, once a day), and the reporting cycle can be set according to actual needs.

[0053] As long as the target service is connected to the SDK of the server, all exception information generated during the operation of the target service can be collected, regardless of whether the error code in the exception information has been recorded on the error code platform of the client. That is, in the method provided in this embodiment, the error code platform does not restrict the error code rules, and any service and error code rules can be accessed without any sense of cost. When there is an error code that has not been stored on the error code platform collected from the client, the newly added error code will be automatically synchronized, and there is no need to configure the newly added error code on the platform in advance.

[0054] Step S103: displaying abnormal data on the abnormal data display page.

[0055] After receiving the abnormal data reported by the server, the error code and error information corresponding to the service are displayed on the abnormal data display page. The abnormal data display page can be a specific actual page or a general term for multiple pages. In response to the interactive operation of the controls in the abnormal data display page, it jumps to other display pages for display.

[0056] For example, the number of error codes corresponding to all services can be displayed on the first page of the error code platform of the client, and the second page can be entered by selecting a service. Each error code and error information corresponding to the selected service are displayed on the second page. In this embodiment, the abnormal data display page includes at least the first page and the second page. Figure 2 As shown, Figure 2 Taking service 1 as an example, the page displays the error code of service 1 and the error description information corresponding to the error code. The error description information includes mapping information, error information template, error code tag, error information, etc.

[0057] The scenario diagram of the data management method corresponding to the embodiment of the present disclosure is as follows Figure 3 As shown, after the configuration page of the client is configured, a configuration data packet is generated and sent to the server, and the server sends abnormal data to the client.

[0058] The data management method provided in this embodiment is applied to the client, generates a configuration data packet in response to the configuration operation on the configuration page, sends the configuration data packet to the server, and receives the abnormal data of the target service sent by the server, wherein the server is used to collect the abnormal information of the target service after the target service is abnormal, and displays the abnormal data on the abnormal data display page of the client. The method provided by the embodiment of the present disclosure adopts a configurable manner to configure the error description information related to the error code, so as to realize the rapid modification of the error information without going online. By displaying the collected abnormal data on the abnormal data display page, it is convenient to query errors according to actual needs, and improve the management efficiency of error codes and the detection efficiency of target services.

[0059] In this embodiment, a data management method is provided, which includes the following steps:

[0060] Step S201, in response to a configuration operation on a configuration page, a configuration data packet is generated and sent to a server.

[0061] Specifically, the above step S201 includes:

[0062] Step S2011: in response to an editing operation on a first error code of a preset service, determining a first error code corresponding to the preset service and first descriptor information corresponding to the preset service.

[0063] The editing operation includes modifying the existing first error code, specifically modifying its error message, error message template, etc. The editing operation may also include manually adding a first error code. The first error code and its corresponding first descriptor information are determined by performing corresponding editing operations in the corresponding page of the client. Assuming that the first error code corresponds to a preset service, the first descriptor information may include the error message template, error message, etc. corresponding to the first error code, which may be determined according to actual settings.

[0064] Step S2012: In response to the mapping operation on the first error code, second descriptor information corresponding to the downstream service of the preset service is determined.

[0065] Among them, the first error description information includes the first descriptor information and the second descriptor information. The downstream service of the preset service is other services that the preset service relies on when executing business logic, which can be internal services (for example, databases, caches, message queues, etc.) or external services (for example, third-party interfaces, etc.). By performing configuration operations on the corresponding configuration page, the second descriptor information of the downstream service is set, and the second descriptor information may include data such as the error code and error information of the downstream service. In the mapping operation, the mapping relationship between the error code of the downstream service and the error information of the downstream service itself can be set, and the mapping relationship between the error code of the downstream service and the error code of the preset service can also be set. Through the mapping operation, a certain error code of the downstream service can be converted into the error code of the preset service, and the error code of the preset service can also be converted into the error code of the preset service. It can also support different business scenarios in the service to be mapped to different error codes and error information.

[0066] Step S202, receiving abnormal data of the target service sent by the server.

[0067] For details, please see Figure 1 Step S102 of the illustrated embodiment will not be described in detail here.

[0068] Step S203: displaying the abnormal data on the abnormal data display page.

[0069] For details, please see Figure 1 Step S103 of the illustrated embodiment will not be described in detail here.

[0070] The data management method provided in this embodiment implements multiple configuration functions on the client, including configuring the first descriptor information of a preset service and the second descriptor information of a downstream service of the preset service, so that when an error occurs in the downstream service, the error code of the downstream service and the error code of the preset service are determined according to the second descriptor information and the first descriptor information, thereby realizing error code conversion between different services.

[0071] In some optional implementations, the above step S2011 includes the following steps:

[0072] Step a1: In response to an interactive operation on a preset service on a configuration page, an error code detail page of the preset service is displayed.

[0073] In this embodiment, the configuration page is the homepage of the error code platform of the client, such as Figure 4 The configuration page shows the number of error codes, success codes, on-duty personnel, and on-duty schedules for each service. The success code refers to the status code returned by the service under what circumstances the request is considered successful. Generally, the default value is 0, but for some special services, other values ​​will be set as success codes, such as 1, 200, etc. Set the preset service to Figure 4 In response to the interactive operation of the service 1 control, service 1 is selected and the page jumps to the error code details page. The error code details page is as follows Figure 2 In the error code details page, you can choose to display the current service error code and downstream service error code corresponding to service 1. Figure 2 The error code details page displays the page for selecting the current service error code. The page displays the current error code list of service 1, including the mapping information corresponding to the error code, error message template, error code tag, error message, etc.

[0074] Step a2: In response to an interactive operation on the first control in the error code details page, display an error code adding page.

[0075] The first control is used to represent the addition of an error code. Figure 2 For example, the first control is an error code add control. In response to the interactive operation on the first control, an error code add page is displayed. Figure 5 As shown, as an example, in response to the interactive operation on the first control, the error code adding page is displayed on the error code details page in the form of a pop-up window.

[0076] It should be noted that the display format of the error code adding page is not specifically limited, and it can also be displayed in the form of pop-up windows, page jumps, etc.

[0077] Step a3, in response to the setting operation of the error code in the error code adding page, determining the first error code, the first error message template, the first error code label and the first error message corresponding to the preset service.

[0078] The error code adding page includes an error code input box, an error message template input box, an error code label input box, and an error message input box. As an example, the error code label input box can be selected from existing labels in the form of a drop-down bar. Labels can be used to indicate the error type corresponding to the error code, and the error type can include business error codes, system error codes, and the like. Different prompt texts can be used for different types of errors, such as warning and error. In response to the interactive operation of the control indicated in the error code adding page, the newly added first error code, as well as the first error message template, the first error code label (i.e., the error code mark), and the first error message corresponding to the first error code are determined, and after determination, they are displayed in the error code details page.

[0079] In some optional implementations, the above step S2012 includes the following steps:

[0080] Step b1, in response to an interactive operation on a second control corresponding to a preset service on a configuration page, displaying an error code list page of the preset service.

[0081] In this embodiment, the configuration page is the homepage of the error code platform of the client, such as Figure 4 The configuration page shows the number of error codes, success codes, duty personnel, duty schedule, etc. corresponding to each service. Figure 4 In response to the interactive operation of the second control corresponding to service 1, the error code list page is displayed, and the second control is Figure 4 The control that represents the error code mapping in each row of services has a corresponding error code mapping control. The page jumps to the error code list page of the preset service, such as Figure 6 As shown. The error code list page displays the error code of the downstream service corresponding to the preset service. The internal error code refers to the error code in the preset service. The downstream service error value is the downstream error code corresponding to the error code in the preset service. On the error code list page, you can select the downstream service corresponding to the preset service through the drop-down option, and then display the error code of the selected downstream service and its corresponding internal error code. You can also edit the error code of the selected downstream service.

[0082] Step b2: In response to an interactive operation on an add mapping control on the error code list page, a downstream error code mapping editing page for a preset service is displayed.

[0083] On the error code list page, there is an add mapping control. You can first select the downstream service to be set, and then select the add mapping control, or you can directly select the add mapping control. In response to the interactive operation of the add mapping control, the downstream error code mapping editing page is displayed. The downstream error code mapping editing page is as follows: Figure 7 As shown. As an example, in response to the interactive operation of adding a mapping control, the downstream error code mapping edit page is displayed in the form of a side pop-up window. It should be noted that the display form of the downstream error code mapping edit page is not specifically limited, and can also be in the form of a pop-up window, page jump, etc.

[0084] Step b3: in response to the setting operation in the downstream error code mapping editing page, determining the correspondence between the first downstream error code of the downstream service of the preset service and the first error code of the preset service.

[0085] Among them, the second descriptor information includes the correspondence between the first downstream error code and the first error code. If the downstream service is pre-selected, there is no need to select the downstream service in the downstream error code mapping editing page. If the downstream service is not pre-selected, select the downstream service in the downstream error code mapping editing page. The downstream error code mapping editing page also includes an internal error code selection box, an error message mapping input box, and a downstream error code input box. Among them, the internal error code represents the first error code in the preset service, the error message maps the error message corresponding to the first error code in the preset service, and the downstream error code is the first downstream error code, which represents the downstream error code corresponding to the first error code. In response to the interactive operation of the determination control, the correspondence between the first downstream error code of the downstream service and the first error code is determined.

[0086] After adding the first error code mapping, the downstream service will be automatically added to the downstream service. By selecting any downstream service, you can configure the internal error code that needs to be mapped to the preset service, supplement the error information, and choose whether to transparently transmit the downstream error code. This implementation method can realize the conversion of the first downstream error code of the downstream service to the first error code of the preset service.

[0087] In some optional implementations, the above step S2012 further includes the following steps:

[0088] Step b4: In response to the interactive operation on the third control in the error code details page, the current service error code mapping editing page is displayed.

[0089] The error code details page is as follows Figure 2 As shown, it can be obtained from Figure 4 Select the preset service in the configuration page shown. As an example, if service 1 is selected, Figure 2 The current error code of service 1 is displayed in Figure 2The mapping control in the operation bar in the middle, in response to the interactive operation of the third control, displays the current service error code mapping editing page, such as Figure 8 shown.

[0090] Step b5: In response to the setting operation on the current service error code mapping editing page, determine the corresponding relationship between the first error code of the preset service and the second downstream error code of the downstream service.

[0091] The second downstream error code corresponds to a preset scenario of the downstream service, and the second descriptor information includes a corresponding relationship between the second downstream error code and the first error code.

[0092] In the current service error code mapping editing page, you can select the downstream service corresponding to the preset service, the internal error code, and the preset scene of the new downstream service by adding a scene control, and then select the external error code (i.e., the second downstream error code) under the preset scene, whether to transparently transmit downstream information, and error information mapping. Among them, the internal error code represents the first error code. One or more preset scenes of the downstream service can be set.

[0093] Exemplarily, the internal error code is set to 123, the preset scenario is set to preset scenario b, and the external error code is set to 50000. When the preset service error code 123 is detected, the error code 123 is converted to 50000 in the preset scenario b of the downstream service.

[0094] In this implementation, a mapping relationship between an error code of a downstream service of a preset service and a first error code of the preset service in a preset scenario is established, thereby achieving error code conversion between the two services.

[0095] In some optional implementations, the above step S2012 further includes the following steps:

[0096] Step b6: In response to the interactive operation on the automatic mapping control in the error code list page, display the configuration mapping page.

[0097] The error code list page is as follows Figure 6 The jump mode can refer to the above step b1, which will not be described again. The error code list page is provided with a control representing automatic mapping rule matching (ie, automatic mapping control), and in response to the interactive operation of the automatic mapping control, the configuration mapping page is displayed. Fig. 9 This is the first page for configuring mapping. The configured mapping rules are displayed on this page. Fig. 9 As shown in the figure, rule1 indicates the name of the established rule. It is configured by expression, where the available variables include error code and error message template content. Fig. 9Rule 1 in indicates that when the first downstream error code satisfies the regular expression (ie, 0<=first downstream error code<2000), the corresponding first error code is determined to be 40001-42000.

[0098] Step b7: In response to a setting operation on a configuration mapping page, determining a correspondence between the first downstream error code and the first error code.

[0099] Fig. 9 The configuration mapping page shown in the figure has a new rule control. In response to the interactive operation of the new rule control, the Fig.10 The configuration mapping page 2 shown in the figure can set the rule name, post-mapping error code, rule expression, post-mapping error information, whether to reuse downstream, etc. In response to the interactive operation of the determination control, the correspondence between the first downstream error code and the first error code is determined.

[0100] Among them, the mapped error code represents the first error code of the preset service, and the rule expression is used to determine whether the first downstream error code is satisfied. When the expression is true, the first downstream error code is mapped to the set first error code. At the same time, the error information after automatic mapping and whether the downstream error information needs to be reused can be configured.

[0101] This implementation is used to convert the first downstream error code of the downstream service into the first error code of the preset service. By setting an expression, the first downstream error codes that meet the expression can be converted in batches. After the error code segment is defined, if the downstream service adds a new error code, the error code will be automatically assigned for mapping in an auto-incremental manner. The conversion efficiency is improved to cope with the situation where there are a large number of first downstream error codes in the downstream service, and error code aggregation can be achieved.

[0102] In some optional implementations, the method described in the above implementations further includes the following steps:

[0103] Step S301, in response to an interactive operation on a fourth control in an error code details page, a configuration marking page is displayed.

[0104] The error code details page is as follows Figure 2 As shown, it can be obtained from Figure 4 The fourth control is used to represent the configuration marking rule control in the error code detail page, and in response to the interactive operation on the fourth control, the configuration marking page is displayed.

[0105] Step S302, in response to the setting operation in the configuration labeling page, determining the correspondence between the first error code and the preset label.

[0106] A new rule control (i.e., a new control) is provided in the configuration marking page. In response to an interactive operation on the new control, a configuration window is displayed, such as Fig.11 As shown, the configuration window is set in the configuration tagging page. In the configuration window, set the rule name, rule expression and output Tag (i.e., preset tag), where the rule name is the rule name and the rule expression represents the code segment to which the error code belongs. When the first error code of the preset service is received, if the first error code satisfies the rule expression, the first error code is marked. In response to the determination control, the correspondence between the first error code and the preset tag is determined, and the error code mark (tag) can be displayed in the error code details page.

[0107] This implementation method can set labels for error codes that meet the conditions by configuring labeling rules, realize automatic labeling function, and facilitate the management of error codes.

[0108] In some optional implementations, if you want to mark an error code of a downstream service of a preset service or an error code thrown by an interface, or convert it to a success code, you can select the downstream service error code in the error code details page, and then mark the downstream service error code. This configuration supports configuring the error code as success and converting the error code to 0, setting the error code log level, etc.

[0109] Dynamic tagging is performed in the error code platform to replace the standard error code rules, so that batch error code processing and warning can be performed through tagging without manual tagging. Preset tags can mark whether the exception supports retries, whether warnings are required, whether error information can be revealed, etc.

[0110] It should be noted that whether to transparently transmit downstream error information in the above text means that the error information mapping does not need to be filled in, and the downstream error information can be directly transparently transmitted.

[0111] The data management method described in the above implementation is applied to the client, and the error code platform is deployed in the client. Various configurations can be performed in the error code platform. Fig.12 As shown in the figure, error_package indicates an error package, error_code indicates an error code, error_rule_log indicates an error rule log, error_rule indicates an error rule, and error_code_mapping indicates an error code mapping. An error package can correspond to multiple error codes, and multiple error rule logs can be associated with one error rule.

[0112] The error code platform can aggregate and match error information, including offline aggregation of error information and real-time matching of error information, to achieve aggregation of errors of the same type. If the acquired abnormal data contains errors of the same type, aggregation processing is performed. The aggregation processing process includes preprocessing, Chinese word segmentation optimization, logic optimization, and multi-language implementation. In the preprocessing process, multiple regular expressions are used to preprocess as many variable contents that may appear in the error information as possible. In the Chinese word segmentation optimization process, special word segmentation processing is performed for Chinese log scenarios. Since most logs are Chinese logs, spaces are rarely used as delimiters. In this solution, Chinese characters and non-Chinese characters are separated. If English characters, numeric characters, and punctuation characters are encountered after Chinese characters, they will be separated into two tokens. In the logic optimization process, after processing a log once, the wildcards in the data will be merged. There may be some manually configured log templates whose length is inconsistent with the actual log length. In order to ensure that the logs are matched as much as possible, this solution adds a tree that removes the first level, matches directly according to the log prefix, and falls back to regular matching when no log is directly matched at the last level.

[0113] In this embodiment, a data management method is provided, which can be used on the server side. Fig.13 is a flow chart of a data management method according to an embodiment of the present disclosure, such as Fig.13 As shown, the process includes the following steps:

[0114] Step S401: receiving a configuration data packet sent by a client.

[0115] The configuration data packet is used to characterize the corresponding relationship between the first error code and the first error description information.

[0116] An error code platform is deployed on the client, and the configuration page is the display page of the error code platform. There are multiple controls on the configuration page. By interacting with different controls on the configuration page, you can jump from the configuration page to other configuration pages to configure the error code. The first error description information may include error information, error information templates, services, etc. corresponding to the error code. Among them, the error information template is template information containing placeholders, and the corresponding error information can be generated by filling the template information according to the error information when an exception occurs in the preset service. The first error description information may not only include error code related information of the preset service, but also include error code related information of the downstream services of the preset service.

[0117] The configuration data packet may include the mapping relationship between the error code and error information of the preset service itself, the mapping relationship between the error code and error information of the downstream service of the preset service, the mapping relationship between the error code of the downstream service and the error code of the preset service, etc.

[0118] Through the configuration operation on the client, a configuration data packet is generated, which may include the correspondence between the error codes and error description information of multiple services. The configuration data packet is sent to the server. Specifically, the SDK of the server pulls the configuration data packet from the error code platform, and the SDK stores the configuration data packet on the server.

[0119] Step S402, collecting abnormal information of the target service after the target service is abnormal.

[0120] The exception information includes the second error code. The server SDK accesses the interface of the target service, detects the target service, and collects the exception information during the operation of the target service. The exception information includes the specific error description actually reported by the service during the actual operation and the second error code corresponding to the error description. As long as the target service accesses the server SDK, all exception information generated during the operation of the target service can be collected, regardless of whether the error code in the exception information has been recorded on the client's error code platform.

[0121] Step S403: determining abnormal data of the target service based on the second error code and the configuration data packet.

[0122] The server obtains the error information template corresponding to the second error code from the configuration data packet, and then fills the error information template based on the error information, and can generate the error information corresponding to the second error code. The abnormal data may include the second error code and the error information corresponding to the second error code. The abnormal data may also include the time when the error occurred, the source of the error, etc. The server reports the abnormal data to the client, and specifically may adopt a regular reporting method (for example, once a day), and the reporting cycle can be set according to actual needs.

[0123] Step S404: sending the abnormal data to the client so that the abnormal data is displayed on the abnormal data display page of the client.

[0124] The server sends the exception data to the client. After receiving the exception data reported by the server, the client displays the error code and error information corresponding to the service on the exception data display page. The exception data display page can be a specific actual page or a general term for multiple pages. In response to the interactive operation of the controls in the exception data display page, it jumps to other display pages for display.

[0125] In some optional implementations, the above step S404 includes the following steps:

[0126] S4041, determine a second error information template corresponding to the second error code from the configuration data packet.

[0127] The configuration data packet stores a correspondence between an error code and an error information template. The corresponding second error information template is obtained from the configuration data packet through the second error code. The second error information template is template information containing a placeholder.

[0128] S4042, filling in the second error information template based on the error data in the exception information, and determining the second error information corresponding to the second error code.

[0129] The exception data includes at least a second error code and a second error message. The error data in the exception message indicates the actual error message reported when an exception occurs in the target service, and the placeholder in the second error message template is filled in according to the parameters in the error message. As an example, suppose the content of the error message template is "The title length is <:NUM:>-<:NUM:> characters, please enter correctly", if the length of the entered title exceeds the set length, the error message displayed according to the actual situation is "The title length is 5-30 characters, please enter correctly".

[0130] The embodiment of the present invention provides a data management system, including an error code platform and a software development kit, through which the configuration data packet on the error code platform is pulled by the software development kit, and abnormal data of the service is reported to the error code platform. Among them, the software development kit can be low-intrusive and non-sensing, without modifying the business code of the service. The architecture of the system is as follows Fig.14 As shown, the access service represents the target service, and the error code SDK is the software development kit. The software development kit reports data to byteio (an object that reads and writes bytes in memory and provides a byte buffer) and the error code service. The difference between the two data reports is that reporting to byteio is periodic reporting, while reporting to the error code service is real-time reporting. The configuration is written to the error code service through the error code platform, and the error code metadata is obtained. The regularly reported data can be stored in the data warehouse software to realize offline data storage. The error code SDK can realize functions such as exception matching, mapping, and logging. Fig.15The following is a diagram of the mapping between services. In the figure, ad.oe.core, ad.ecp.creation, and ad.cdp.core represent different services. When an exception occurs at the bottom layer, the corresponding error code is 10010. In the service ad.oe.core that it calls, the error code 10010 is mapped to 40000, and the corresponding error message is "the plan does not exist." When the service ad.ecp.creation calls the service ad.oe.core, the error code 40000 is converted to 10340001, and the error message is still "the plan does not exist." When ad.cdp.core calls the service ad.oe.core, the error code 400000 is converted to 10540001, and the error message is converted to "the advertisement does not exist." The above mapping processes are all achieved by presetting the mapping relationship between the error codes of each service.

[0131] The data management system provided by this embodiment reduces complexity through configuration, and can quickly configure the mapping of error codes and error information, which is convenient for handling the original exceptions thrown by the downstream, without the need to change the code every time a new exception is added. The configuration definition of the same service is once and all upstream services can reuse the configuration. It is highly maintainable and can automatically synchronize new error codes to avoid omissions. New special error codes can be automatically synchronized and marked by the person in charge with one click. It supports seamless access and low-cost SDK access. Compared with the old platform, the access cost is extremely low, and full-platform service access can be quickly achieved. It supports visual stability capabilities, can quickly query the monitoring and logs corresponding to the error code, and can support one-click injection of alarms. Through the collection of full-link error codes, link attribution capabilities can be supported, and error reporting services and scenarios can be quickly located through error codes.

[0132] In this embodiment, a data management device is also provided, which is used to implement the above-mentioned embodiments and implementation methods, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0133] This embodiment provides a data management device, such as Fig.16 As shown, including:

[0134] The data packet generation module 501 is used to generate a configuration data packet in response to a configuration operation on the configuration page, and send the configuration data packet to the server, wherein the configuration data packet is used to represent the correspondence between the first error code and the first error description information;

[0135] A data receiving module 502 is used to receive abnormal data of a target service sent by the server, wherein the server is used to collect abnormal information of the target service after the target service is abnormal, wherein the abnormal information includes a second error code, and the abnormal data is obtained based on the second error code and the configuration data packet;

[0136] The data display module 503 is used to display the abnormal data on the abnormal data display page.

[0137] In some optional implementations, the data packet generation module 501 includes:

[0138] an error code editing module, configured to determine, in response to an editing operation on a first error code of a preset service, a first error code corresponding to the preset service and first descriptor information corresponding to the preset service;

[0139] The error code mapping module is used to determine the second descriptor information corresponding to the downstream service of the preset service in response to the mapping operation of the first error code, wherein the first error description information includes the first descriptor information and the second descriptor information.

[0140] In some optional implementations, the error code editing module includes:

[0141] A first editing unit, configured to display an error code detail page of the preset service in response to an interactive operation on the preset service on the configuration page;

[0142] A second editing unit, configured to display an error code adding page in response to an interactive operation on the first control in the error code details page;

[0143] The third editing unit is used to determine the first error code, the first error message template, the first error code label and the first error message corresponding to the preset service in response to the setting operation of the error code in the error code adding page.

[0144] In some optional implementations, the error code mapping module includes:

[0145] A second control response unit, configured to display an error code list page of the preset service in response to an interactive operation on the second control corresponding to the preset service on the configuration page;

[0146] An adding control response unit, configured to display a downstream error code mapping editing page for the preset service in response to an interactive operation on an adding mapping control on the error code list page;

[0147] A first mapping determination unit is used to determine the correspondence between the first downstream error code of the downstream service of the preset service and the first error code of the preset service in response to a setting operation in the downstream error code mapping editing page, and the second descriptor information includes the correspondence between the first downstream error code and the first error code.

[0148] In some optional implementations, the error code mapping module further includes:

[0149] A third control response unit, configured to display a current service error code mapping edit page in response to an interactive operation on a third control in the error code details page;

[0150] A second mapping determination unit is used to determine the correspondence between the first error code of the preset service and the second downstream error code of the downstream service in response to the setting operation on the current service error code mapping editing page, the second downstream error code corresponds to the preset scenario of the downstream service, and the second descriptor information includes the correspondence between the second downstream error code and the first error code.

[0151] In some optional implementations, the error code mapping module further includes:

[0152] An automatic mapping control response unit, configured to display a configuration mapping page in response to an interactive operation on the automatic mapping control in the error code list page;

[0153] The third mapping determination unit is configured to determine a correspondence between the first downstream error code and the first error code in response to a setting operation on the configuration mapping page.

[0154] In some optional embodiments, the device further comprises:

[0155] A fourth control response module, configured to display a configuration marking page in response to an interactive operation on a fourth control in the error code details page;

[0156] The marking determination module is used to determine the corresponding relationship between the first error code and the preset label in response to the setting operation in the configuration marking page.

[0157] This embodiment provides a data management device, such as Fig.17 As shown, including:

[0158] The data packet receiving module 601 is used to receive a configuration data packet sent by the client, where the configuration data packet is used to characterize the correspondence between the first error code and the first error description information;

[0159] An information collection module 602 is used to collect abnormal information of the target service after the target service is abnormal, and the abnormal information includes a second error code;

[0160] A data determination module 603, configured to determine abnormal data of a target service based on the second error code and the configuration data packet;

[0161] The abnormal data sending module 604 is used to send the abnormal data to the client so that the abnormal data can be displayed on the abnormal data display page of the client.

[0162] In some optional implementations, the data determination module 603 includes:

[0163] a template determining unit, configured to determine a second error information template corresponding to the second error code from the configuration data packet;

[0164] An error information determination unit is used to fill in the second error information template based on the error data in the abnormal information, and determine the second error information corresponding to the second error code, wherein the abnormal data at least includes the second error code and the second error information.

[0165] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0166] The device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0167] The embodiment of the present disclosure also provides a computer device having the above-mentioned data management device.

[0168] See also Fig.18 , Fig.18 is a schematic diagram of a computer device provided by an optional embodiment of the present disclosure, such as Fig.18As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Fig.18 A processor 10 is taken as an example.

[0169] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0170] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0171] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0172] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0173] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0174] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0175] A part of the present disclosure may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present disclosure through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes, but is not limited to, source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to the computer.

[0176] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the present invention.

Claims

1. A data management method, characterized in that: Applied to a client, the method comprises: In response to a configuration operation on the configuration page, a configuration data packet is generated, and the configuration data packet is sent to the server, wherein the configuration data packet is used to characterize a correspondence between the first error code and the first error description information; receiving abnormal data of a target service sent by the server, the server being used to collect abnormal information of the target service after the target service is abnormal, the abnormal information including a second error code, and the abnormal data being obtained based on the second error code and the configuration data packet; The abnormal data is displayed on the abnormal data display page.

2. The method according to claim 1, characterized in that The generating of a configuration data packet in response to a configuration operation on a configuration page includes: In response to an editing operation on a first error code of a preset service, determining a first error code corresponding to the preset service and first descriptor information corresponding to the preset service; In response to a mapping operation on the first error code, second descriptor information corresponding to a downstream service of the preset service is determined, where the first error description information includes the first descriptor information and the second descriptor information.

3. The method according to claim 2, characterized in that The step of determining, in response to an editing operation on a first error code of a preset service, a first error code corresponding to the preset service and first descriptor information corresponding to the preset service comprises: In response to an interactive operation on the preset service on the configuration page, displaying an error code detail page of the preset service; In response to an interactive operation on a first control in the error code details page, displaying an error code adding page; In response to the setting operation of the error code in the error code adding page, a first error code, a first error message template, a first error code label and a first error message corresponding to the preset service are determined.

4. The method according to claim 3, characterized in that The determining, in response to the mapping operation on the first error code, second descriptor information corresponding to the downstream service of the preset service includes: In response to an interactive operation on a second control corresponding to the preset service on the configuration page, displaying an error code list page of the preset service; In response to an interactive operation on an add mapping control on the error code list page, displaying a downstream error code mapping edit page for the preset service; In response to the setting operation in the downstream error code mapping editing page, the correspondence between the first downstream error code of the downstream service of the preset service and the first error code of the preset service is determined, and the second descriptor information includes the correspondence between the first downstream error code and the first error code.

5. The method according to claim 4, characterized in that The determining, in response to the mapping operation on the first error code, second descriptor information corresponding to the downstream service of the preset service further includes: In response to an interactive operation on a third control in the error code details page, displaying a current service error code mapping edit page; In response to the setting operation on the current service error code mapping editing page, the correspondence between the first error code of the preset service and the second downstream error code of the downstream service is determined, the second downstream error code corresponds to the preset scenario of the downstream service, and the second descriptor information includes the correspondence between the second downstream error code and the first error code.

6. The method according to claim 4, characterized in that The determining, in response to the mapping operation on the first error code, second descriptor information corresponding to the downstream service of the preset service further includes: In response to an interactive operation on an automatic mapping control in the error code list page, displaying a configuration mapping page; In response to a setting operation on the configuration mapping page, a corresponding relationship between the first downstream error code and the first error code is determined.

7. The method according to claim 3, characterized in that The method further comprises: In response to an interactive operation on a fourth control in the error code details page, displaying a configuration marking page; In response to a setting operation in the configuration marking page, a corresponding relationship between the first error code and a preset label is determined.

8. A data management method, characterized in that: Applied to the server, the method includes: Receive a configuration data packet sent by the client, where the configuration data packet is used to represent a correspondence between a first error code and first error description information; After the target service is abnormal, collect the abnormal information of the target service, wherein the abnormal information includes a second error code; Determine abnormal data of the target service based on the second error code and the configuration data packet; The abnormal data is sent to the client, so that the abnormal data is displayed on an abnormal data display page of the client.

9. The method according to claim 8, characterized in that The determining the abnormal data of the target service based on the second error code and the configuration data packet includes: Determining a second error information template corresponding to the second error code from the configuration data packet; The second error information template is filled based on the error data in the abnormal information to determine the second error information corresponding to the second error code, and the abnormal data at least includes the second error code and the second error information.

10. A data management device, characterized in that: The device comprises: A data packet generating module, used to generate a configuration data packet in response to a configuration operation on a configuration page, and send the configuration data packet to a server, wherein the configuration data packet is used to characterize a correspondence between a first error code and first error description information; a data receiving module, configured to receive abnormal data of a target service sent by the server, wherein the server is configured to collect abnormal information of the target service after the target service is abnormal, wherein the abnormal information includes a second error code, and the abnormal data is obtained based on the second error code and the configuration data packet; The data display module is used to display the abnormal data on the abnormal data display page.

11. A data management device, characterized in that: The device comprises: A data packet receiving module, used to receive a configuration data packet sent by a client, wherein the configuration data packet is used to characterize a correspondence between a first error code and first error description information; An information collection module, used for collecting abnormal information of the target service after the target service is abnormal, wherein the abnormal information includes a second error code; a data determination module, configured to determine abnormal data of a target service based on the second error code and the configuration data packet; The abnormal data sending module is used to send the abnormal data to the client so that the abnormal data can be displayed on the abnormal data display page of the client.

12. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the data management method according to any one of claims 1 to 9 by executing the computer instructions.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the data management method according to any one of claims 1 to 9.

14. A computer program product, characterized in that The method comprises computer instructions for causing a computer to execute the data management method according to any one of claims 1 to 9.

Images