Monitoring Method for Business System and Related Devices

Abstract

The present application provides a monitoring method for a service system and related devices in the field of cloud computing. In the technical solution provided by the present application, when a service node provides a service, it reports the business scenario information associated with the current service to the database server, so that when a problem occurs with the service node, the business scenario affected by the problem of the service node can be determined based on the business scenario information, thereby enabling accurate positioning of the affected business scenario.

Description

Technical Field

[0001] This application relates to the field of cloud computing, and in particular to a monitoring method and related devices for business systems. Background Art

[0002] With the development of the Internet, the means of transactions have changed from offline to online, and every link of the business scenario is carried out on the network. Therefore, in order to ensure the normal and stable operation of the business scenario, monitoring technology is often used to monitor the whole process of the business scenario. Once a problem occurs in a certain business scenario during a transaction, the monitoring system can discover it in time.

[0003] A monitoring method includes: collecting multi-dimensional data such as the user layer and the system layer by a service node, feeding the data back to the front-end device, and monitoring the running status of a certain service or system from multiple dimensions.

[0004] Although this method can discover the service node with problems, it can only know that the data transmitted by the service node is incorrect, and cannot know which specific business scenario or scenarios are affected. Summary of the Invention

[0005] This application provides a monitoring method and related devices for business systems in the field of cloud computing or distributed systems, which can accurately locate the affected business scenarios according to the problem service nodes.

[0006] In a first aspect, this application provides a monitoring method for a business system, including:

[0007] A service node receives a first piece of information, where the first piece of information is used to request to call the service on the service node; the service node obtains the current business scenario information of the service according to the first piece of information; the service node sends business information to a database server, and the business information includes the identification information of the service node, the current business scenario information, the time information when the service node provides the service, and the duration information when the service node provides the service.

[0008] In this method, the service node sends the business information to the data server, so that the situation of link calls and the running status of each service node can be intuitively seen based on the business information, and thus the affected business scenarios can be locked when a problem occurs in the service node.

[0009] Combined with the method of the first aspect, in the first possible implementation manner, the service node obtains the current business scenario information of the service according to the first information, including: when the first information is the information sent by the upstream service node of the service node based on the upstream service and the business scenario information of the upstream service is included in the first information, the service node determines the business scenario information of the upstream service as the current business scenario information; when the first information is the information sent by the upstream service node of the service node based on the upstream service, the business scenario information of the upstream service is not included in the first information, and the business scenario information is set for the service in the service node, the service node determines the business scenario information set for the service in the service node as the current business scenario information; when the first information is the information sent by the front-end device and the business scenario information is set for the service in the service node, the service node determines the business scenario information set for the service in the service node as the current business scenario information.

[0010] This implementation manner can determine the business scenario information of the current service. Among them, preferentially inheriting the business scenario information of the previous service node can ensure the accuracy of business scenario coloring.

[0011] Combined with the first aspect or the first possible implementation manner, in the second possible implementation manner, the service node sends a second information to the downstream service node based on the first information, and the second information is used to request to call the downstream service on the downstream service node, and the current business scenario information is included in the second information.

[0012] In this method, the second information is sent to the downstream service node by the first information, and the service node is continuously called by sending information to ensure the continuous transmission of the business scenario information.

[0013] In the second aspect, the present application provides a monitoring method for a business system, including:

[0014] The database server receives the business information from the service node, and the business information includes the identification information of the service node, the business scenario information, and the key information. The key information includes the time when the service node obtains the business scenario information and the duration of providing services for the business corresponding to the business scenario information; the database server stores the business information; the database server sends the business information to the front-end device.

[0015] In this method, the key information in the service information can be collected by a real-time time generation component. The collected data is transmitted from the service node to the database server, and then the service information is sent to the front end. The identification information, tags, Chinese meanings of the tags, service time, and duration of the service node can be intuitively displayed on the front-end device for operation and maintenance personnel or technical personnel to view.

[0016] In this method, when the service node collects data, different methods are used to classify the data into three categories: metric type, link type, and system type for collection, and then sent to the corresponding gateway. The database server classifies and stores the service information according to these three types of data.

[0017] In one example, the "payment transaction service" is set with the tag "100", and the Chinese meaning of the tag is "payment transaction service". When a problem occurs with the service node corresponding to the "blacklist check" service, according to the coloring operation during the previous service, the service node can obtain the tag "100" corresponding to the "blacklist check" and the Chinese meaning of the tag "payment transaction service". Based on the tag, the link called during the service operation is found, and the service scenario affected by the problem service node and the relevant information of the link called by the service scenario are displayed on the front-end device.

[0018] Combined with the method of the second aspect, in the first possible implementation manner, the database server receives the service information request information from the front-end device; the database server sends the service information to the front-end device, including: the database server sends the service information to the front-end device in response to the service information request information.

[0019] In this method, when operation and maintenance personnel or technical personnel want to query the current service operation situation, by sending a request for data call to the database server, after the database server receives the call request, it sends the service information data to the front-end device for display. Operation and maintenance personnel or technical personnel can then obtain the service operation situation from the front-end device, thereby discovering the problem node and the service scenario where it is located.

[0020] In a third aspect, the present application provides a monitoring method for a service system, including: the front-end device receives service information from the database server, where the service information includes the identification information of the service node, the service scenario information, and key information, and the key information includes the time when the service node obtains the service scenario information and the duration of providing services for the service corresponding to the service scenario information; the front-end device displays the service information.

[0021] In this method, the front-end device can improve the query efficiency through an aggregation mechanism. Before querying, it aggregates according to specific rules (such as summarizing the data of one day according to the service dimension, etc.) to reduce the consumption of traversing and querying item by item.

[0022] In this method, the front-end device can also be customized, providing the display end with the front-end display ability that can be dragged and set arbitrarily, and reusing the open-source software ability. The front-end device displays the identification information of the service node, the business scenario information, and the key information in the form of a table, a topology, or other forms.

[0023] Combined with the method of the third aspect, in the first possible implementation manner, before the front-end device receives the business information from the database server, the method further includes: the front-end device sends business information request information to the database server.

[0024] In this method, the operation and maintenance personnel or technical personnel can obtain business information by actively sending request information to the database server.

[0025] In a fourth aspect, the present application further provides a service node, including each functional module for implementing the method in the first aspect. Each functional module can be implemented in software and / or hardware.

[0026] As an example, the device may include: a first receiving module, an obtaining module, and a first sending module.

[0027] Among them, the first receiving module can be used to receive the first information, and the first information is used to request to call the service on the service node. The obtaining module can be used to obtain the current business scenario information of the service according to the first information. The first sending module can be used to send business information to the database server, and the business information includes the identification information of the service node, the current business scenario information, the time information when the service node provides the service, and the duration information when the service node provides the service.

[0028] Optionally, when the first information is the information sent by the upstream service node of the service node based on the upstream service, and the upstream service scenario information is included in the first information, the obtaining module determines the upstream service scenario information as the current business scenario information; when the first information is the information sent by the upstream service node of the service node based on the upstream service, the upstream service scenario information is not included in the first information, and the service scenario information is set for the service in the service node, the obtaining module determines the service scenario information set for the service in the service node as the current business scenario information; when the first information is the information sent by the front-end device, and the service scenario information is set for the service in the service node, the obtaining module determines the service scenario information set for the service in the service node as the current business scenario information.

[0029] Optionally, the first sending module may further send second information to a downstream service node based on the first information, where the second information is used to request to invoke a downstream service on the downstream service node, and the second information includes the current service scenario information.

[0030] In a fifth aspect, the present application further provides a service invocation device, which may include a memory and a processor coupled to the memory.

[0031] The processor is configured to execute program instructions to implement the instructions executed by the method in the first aspect; the memory is used to store the instructions executed by the processor or store the input data required for the processor to run the instructions or store the data generated after the processor runs the instructions.

[0032] The device may be a service node or a chip applied to a service node, etc.

[0033] In a sixth aspect, the present application further provides a database server, including each functional module for implementing the method in the second aspect. Each functional module may be implemented in a software and / or hardware manner.

[0034] As an example, the device may include: a second receiving module, a storage module, and a second sending module.

[0035] Among them, the second receiving module may be configured to receive service information from a service node, where the service information includes the identification information of the service node, the service scenario information, and key information, and the key information includes the time when the service node obtains the service scenario information and the duration of providing services for the service corresponding to the service scenario information. The storage module may be configured to store the service information. The second sending module may be configured to send the service information to a front-end device.

[0036] Optionally, the second receiving module may further receive service information request information from the front-end device; the second sending module may further send the service information to the front-end device, including sending the service information to the front-end device in response to the service information request information.

[0037] In a seventh aspect, the present application further provides a database service device, which may include a memory and a processor coupled to the memory.

[0038] The processor is configured to execute program instructions to implement the instructions executed by the method in the second aspect; the memory is used to store the instructions executed by the processor or store the input data required for the processor to run the instructions or store the data generated after the processor runs the instructions.

[0039] The device may be a database server or a chip applied to a database server, etc.

[0040] In an eighth aspect, the present application further provides a front-end device, which includes various functional modules for implementing the method in the third aspect. Each functional module can be implemented in a software and / or hardware manner.

[0041] As an example, the device may include: a third receiving module and a display module.

[0042] Among them, the third receiving module can be used to receive service information from a database server. The service information includes the identification information of the service node, the service scenario information, and key information. The key information includes the time when the service node obtains the service scenario information and the duration of providing services for the service corresponding to the service scenario information. The display module can be used to display the service information.

[0043] Optionally, the device may further include a third sending module, which can be used to send service information request information to the database server before receiving service information from the database server.

[0044] In a ninth aspect, the present application further provides a front-end device, which may include a memory and a processor coupled to the memory.

[0045] The processor is used to execute program instructions to implement the instructions executed by the method in the third aspect; the memory is used to store the instructions executed by the processor or store the input data required for the processor to run the instructions or store the data generated after the processor runs the instructions.

[0046] The device may be a front-end device or a chip applied to a front-end device, etc.

[0047] In a tenth aspect, the present application provides a computer-readable storage medium, which stores program code for a processor to execute. The program code includes instructions for implementing the method in the first, second, or third aspect.

[0048] In an eleventh aspect, the present application provides a computer program product, which, when running on a processor, enables the monitoring device of the service scenario to implement the method in the first, second, or third aspect.

[0049] It can be understood that the technical effects that can be achieved by the monitoring device of the service scenario, the computer-readable storage medium, and the computer program product provided by the present application can refer to the first, second, or third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0051] Figure 1 It is a schematic diagram of the business system architecture.

[0052] Figure 2 It is a schematic flowchart of the configuration method of the service node according to an embodiment of the present application.

[0053] Figure 3 It is a schematic flowchart applied in the monitoring method of the business system provided by an embodiment of the present application.

[0054] Figure 4 It is a flowchart of the dyeing mechanism provided by an embodiment of the present application.

[0055] Figure 5 It is a schematic flowchart of the monitoring method of the business system provided by another embodiment of the present application.

[0056] Figure 6 It is a schematic flowchart of the monitoring method of the business system provided by yet another embodiment of the present application.

[0057] Figure 7 It is a schematic diagram in tabular form for the front-end device to display business information.

[0058] Figure 8 It is a schematic diagram in topological form for the front-end device to display business information.

[0059] Figure 9 It is a schematic diagram of the service node provided by an embodiment of the present application.

[0060] Figure 10 It is a schematic diagram of the database server provided by an embodiment of the present application.

[0061] Figure 11 It is a schematic diagram of the front-end device provided by an embodiment of the present application.

[0062] Figure 12 It is a schematic diagram of the computing device provided by another embodiment of the present application.

[0063] Through the above-mentioned drawings, specific embodiments of the present application have been shown, and there will be more detailed descriptions hereinafter. These drawings and textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed Embodiments

[0064] Exemplary embodiments will be described in detail herein, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. On the contrary, they are merely examples of apparatuses and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0065] The technical solution of the present application can be applied to the following scenario: when a business system has problems, how to trace the root cause link that causes the problems in the business system.

[0066] The present application provides a monitoring method for a business system, and this method can be applicable to Figure 1 the schematic diagram of the business system architecture shown. Figure 1 The system shown includes multiple front-end devices 103, a database server 102, and multiple service nodes 101.

[0067] The front-end device 103 is a device with information reading and displaying functions. This device can be a device with data processing capabilities such as a computer or a mobile terminal, including but not limited to a computer in a bank used to implement transactions or view a certain service and the system call link, and can monitor the operating conditions in different dimensions.

[0068] The database server 102 is a server provided with a database and capable of receiving, storing, and sending data, and is connected to the service node 101 and the front-end device 103 through network communication.

[0069] The service node 101 is an entity device or a virtual device used to implement the services required by the business. The entity device can be a device with data collection, operation, processing, and storage capabilities such as a computer or a mobile terminal.

[0070] Such as Figure 1As shown, as the user triggers a transaction service, the service starts. The service node continuously invokes the next service node. The service node transmits the first information to the downstream service node, and the next service node transmits the second information to an even more downstream service node. The first information and the second information are used to complete the node invocation and enable the current service node to obtain business scenario information. After the service node 101 collects data, it can upload the data to the database server 102. The database server 102 receives the relevant business information sent from the service node 101 and then stores the data in the database. At the same time, the database server 102 is connected to the front-end device 103 through network communication. When an operation and maintenance personnel or a developer has a query requirement, a call request is sent to the database server 102 through the front-end device 103. After the database server 102 sends the data to the front-end device 103, the front-end device 103 receives the business information and displays the overall operation status of a certain service or system.

[0071] It should be noted that in actual operations, the front-end device 103 used by technicians and the front-end device 103 used by customers are usually not the same front-end device. The front-end device used by customers is used to trigger the business system, while the front-end device of technicians is used to view the call link of the transaction.

[0072] Figure 1 In the business system shown, when the implementation of a service requires the mutual invocation of a large number of service nodes, a long call link will be generated. This makes it difficult to trace the root cause of problems during the service implementation process and difficult to know which business scenarios are specifically affected by the problematic service node.

[0073] To address the above problems, the present application provides a monitoring method for a business system. In the method provided by the present application, from a business perspective, the call link in the business scenario is monitored to trace the root cause of problems and find the business scenarios affected by the problematic service node.

[0074] Figure 2 The following is a schematic flowchart of a configuration method for a service node according to an embodiment of the present application. The configuration method includes the following steps:

[0075] S210, introduce a software development kit (SDK) in the service node

[0076] The staff or technician imports the software development kit (SDK) into the service node, including but not limited to methods such as "copy" or "download".

[0077] S220, set business scenario information through the SDK.

[0078] For example, run the SDK to set the business scenario information in the service node.

[0079] In this embodiment, the business scenario information may include the type of business transaction. One type of transaction corresponds to one business scenario, and different business scenarios provide different services, which are deployed on specific nodes.

[0080] For example, in banking, transaction types (or business scenarios) include loan business, deposit business, securities business, payment transactions, etc. Taking the "payment transaction business" as an example, the "payment transaction business" is a type of transaction and also a business scenario. To implement this business, the services required are: "protocol check", "blacklist check", "customer card number check", "account status check", "account balance check", etc., and each service is deployed on the corresponding node.

[0081] As an example, setting business scenario information through the SDK may include: setting corresponding annotations for the services corresponding to the specific entry when a transaction occurs through the SDK. The annotations include but are not limited to the following:

[0082] 1) Label type, mainly used to complete the label type identification of the unique business scenario;

[0083] 2) Chinese meaning of the label, used to more clearly distinguish and view the business scenario.

[0084] In this example, the setting of business scenario information can be completed through this annotation. For example, set an annotation for the service entry "protocol check" of the "payment transaction business". The annotation contains the label type "100" and the Chinese meaning of the label is "payment transaction business".

[0085] Generally speaking, for different transaction types, their service entries are different, so the set annotations are different, and the corresponding business scenario information is also different.

[0086] In special cases, there may be a situation where the service node corresponding to the service entry may correspond to multiple transaction types. In this case, no annotation will be set for the service entry.

[0087] Actually, by introducing the SDK to set annotations, there may also be a situation where the node is not introduced.

[0088] For example, in the "tagging" link, the service entry "protocol check" corresponds to multiple transaction types, and the service nodes corresponding to the "customer card number check" and "account balance query" services are not introduced (there is a situation where each node is not introduced). Therefore, the service nodes where annotations can be set in the "payment transaction business" service may only be the service nodes corresponding to the "blacklist check" and "account status check" services.

[0089] It is understandable that one or more annotations can be set for a business scenario according to the characteristics of the transaction type. In this embodiment, only one annotation is set for simplicity of description.

[0090] It is understandable that Figure 2 The manner shown is only an exemplary implementation manner for setting business scenario information for the services in the service node. The present application can also set business scenario information in other ways. For example, it can be set when the R & D personnel develop the service code.

[0091] For the services that have been deployed on the service node in this way through the SDK, it is more convenient to set the business scenario information.

[0092] Figure 3 It is a schematic flowchart applied in the monitoring method of the business system provided in an embodiment of the present application. The monitoring method includes the following steps:

[0093] S310, the service node receives the first information, and the first information is used to request to call the service on the service node.

[0094] As an example, the service node can be Figure 1 the first service node called to implement the current business in the system shown, that is, the service on this service node is the service required to implement the current business. For example, the service node receives the first information sent by the user through the front-end device.

[0095] As another example, the service node can be the service node called by other service nodes to implement the current business. For example, the service node receives the first information from other service nodes.

[0096] S320, the service node obtains the business scenario information of the service. The business scenario information can indicate the business scenario.

[0097] As an example, as Figure 4 shown, when the service node obtains the business scenario information of the service, if there is an upstream service node for the service node (that is, the service node that sends the service call to the service node), the service node preferentially inherits the business scenario information passed by the upstream service node, that is, obtains the business scenario information; if there is no upstream service node for the service node or the upstream service node does not pass the business scenario information, then the service node determines whether the first service is set with business scenario information; if the service in the service node is set with business scenario information, then obtain the business scenario information; if the service in the service node is not set with business scenario information, then the acquisition of the business scenario information fails, and at this time, the business scenario information can be determined to be empty.

[0098] In this embodiment, the service label information is passed down one by one according to the call order of the service nodes. The service nodes passed by the same business scenario information belong to the service nodes of the same business scenario. In this embodiment, this mechanism is also called the coloring mechanism of the service nodes.

[0099] Taking the implementation of the "payment transaction service" which successively calls "protocol check", "blacklist check", "customer card number check", "account status check", and "account balance check" as an example, the method steps for the service nodes to obtain the business scenario information are described below.

[0100] (1) In the payment transaction service, the service entry starts from the "protocol check". The service providing the "protocol check" undergoes scanning and parsing by the service nodes to obtain the corresponding label type "100" and the Chinese meaning of the label "payment transaction service", and writes the above information into the context. Then, the context is set into the message header, and the data is transmitted by the message header, and the above information is sent to the service node where the "blacklist check" service is located.

[0101] The service node where the "blacklist check" is located inherits the business scenario information of the upstream service node, writes the data into the context in the same way, and sends it to the service node where the downstream service is located through the message.

[0102] By analogy, the subsequent services "customer card number check", "account status check", and "account balance check" are colored in the same way.

[0103] (2) If the "protocol check" service is the starting service for multiple transaction types, there may be multiple business scenario information for this service. In this case, it is impossible to determine which one of these multiple pieces of business scenario information is correct, so the business scenario information can be set to "null". In this way, the service node where the "blacklist check" service is located obtains the business scenario information from the information carried by this node itself and passes it to the service node where the subsequent service is located.

[0104] (3) If there are more than two service nodes in a business (such as the first two services) corresponding to multiple business scenario information, or because they are not introduced in the "labeling" link, then the above service nodes do not have corresponding business scenario information.

[0105] Service nodes where services such as "protocol check" and "blacklist check" are located each correspond to multiple business scenario information. That is, the node where the "protocol check" service is located does not set the corresponding business scenario information. The first information is transmitted to the service node corresponding to the "blacklist check". The first information does not contain the business scenario information in the upstream service node, and the service node where the current "blacklist check" is located itself does not contain business scenario information either. In this business, service nodes such as "protocol check" and "blacklist check" that do not carry business scenario information themselves will not appear in the subsequent displayed link information.

[0106] The following introduces the method for a service node to obtain business scenario information when the business scenario information is set through annotations.

[0107] As an example, after setting corresponding annotations for the service corresponding to the specific entry during a transaction, during the actual operation of the transaction, the service node samples data in real time through a data collection module, and with the help of the underlying architecture, including but not limited to the scanning mechanism of frameworks such as "spring", scans the annotations of the data. After scanning, the annotations set for the current node can be obtained.

[0108] After scanning and obtaining the annotations of the current node, the service node parses the annotations to "translate" the business scenario of the current service, that is, obtains the label type and the Chinese meaning of the label in the annotations.

[0109] S330, the service node sends business information to the database server. The business information includes the identification information of the service node, the business scenario information, and key information. The key information includes the time when the service node obtains the business scenario information and the duration of providing services for the business corresponding to the business scenario information.

[0110] As an example, after parsing the annotations to obtain the label type and the Chinese meaning of the label, the service node sets different variables to temporarily store the corresponding business scenario information for the real-time sampled data.

[0111] Next, the operation module and the control module in the service node write the business scenario information into the context. The context here is used to carry the information required for monitoring, that is, to transmit data.

[0112] The service node sets the context into the message header and sends the message header to the database. The message header, as a carrier for transmitting data, is used to transmit information between different nodes in the network.

[0113] There can also be a real-time time generation component in the service node, which records the start time, end time, and elapsed time of the current business passing through the service node through this component.

[0114] After the service node obtains the service information, it can first cache it locally at a certain granularity and then send it in batches to reduce the network consumption caused by sending every time the service information is obtained.

[0115] In a possible implementation, the service node can send the service information regularly, or send it at a certain frequency. For example, it can send it once every 10 seconds.

[0116] In the embodiments of the present application, if the service node needs to send information for requesting to call other services to other service nodes to implement the current service, the service node also needs to execute S340.

[0117] In this embodiment, optionally, the service node can also send the second information to the downstream service node based on the first information. The second information is used to request to call the second service, and the second information includes the service scenario information. Wherein, the second service is the service called by the first service.

[0118] Figure 5 It is a schematic flowchart of a monitoring method for a service system provided in another embodiment of the present application. As Figure 5 shown, the database server receives the service information transmitted from the service node, stores the data carrying this information, and sends the service information to the front-end device after the front-end device sends a call request to the database server, or the database actively sends the service information to the front-end device regularly.

[0119] This monitoring method includes the following steps:

[0120] S510, the database server receives the service information sent by the service node. The service information includes the identification information of the service node, the service scenario information, and key information. The key information includes the time when the service node obtains the service scenario information and the duration of providing services for the service corresponding to the service scenario information.

[0121] As an example, the service scenario information includes, but is not limited to, the label type and the Chinese meaning of the label.

[0122] S520, the database server stores the service information.

[0123] After receiving the service information, the database server can classify and store the collected information according to certain rules. The purpose of doing this is to improve the query efficiency during subsequent queries and prevent the problem of large-scale unqueryability caused by failures such as the monitoring database, thereby improving high availability.

[0124] S530, the database server sends the service information to the front-end device.

[0125] As an example, the database server can send service information to the front-end device regularly or at a preset time.

[0126] As another example, when the front-end device sends a service information call request to the database server, the database server sends service information to the front-end device.

[0127] Figure 6 It is a schematic flowchart of a monitoring method for a service system according to another embodiment of the present application. As Figure 6 shown, after the front-end device sends a request to the database server, it receives service information from the database server or the database server actively sends service information to the front-end device regularly. After receiving the information, the front-end device displays the service information on the display.

[0128] The monitoring method includes the following steps:

[0129] S610, the front-end device receives service information from the database server. The service information includes the identification information of the service node, the service scenario information, and key information. The key information includes the time when the service node obtains the service scenario information and the duration of providing services for the service corresponding to the service scenario information.

[0130] In some possible implementation manners, the database server can actively send service information to the front-end device.

[0131] In some other possible implementation manners, the front-end device first sends a service information call request to the database server and then receives the service information sent by the database server based on the call request.

[0132] For example, when an operation and maintenance personnel or a developer has a query requirement, the front-end device 103 sends a service information call request to the server 102 to call the service information stored in the database server.

[0133] S620, the front-end device displays the service information.

[0134] The front-end device displays the received service information through the display screen, facilitating the operation and maintenance personnel or the developer to find the problem nodes affecting the transaction according to the service information displayed by the front-end device.

[0135] The following is an example. If in an actual business service, the data collected by the service node corresponding to the "account status check" service is incorrect, then the service node will report an error, and the specific service scenario can be traced according to the label of the service node, which is divided into two cases.

[0136] (1) Based on the previous coloring situation, "Account Status Check" only corresponds to one business scenario, namely the "Payment Transaction Business" service. Then, according to the label "100", locate the "Payment Transaction Business" service, query all relevant data based on the label, and sort the data in ascending order according to the time when the service node calls the data.

[0137] On the front-end device, the call link of the "Payment Transaction Business" service and the identification information of the corresponding service nodes on the link will be displayed. Additionally, relevant time nodes and elapsed times will also be shown. The service node compares the current information with the error information, and on the front-end device, it can intuitively show which service node in which business scenario has a problem and which business scenarios are affected.

[0138] (2) Based on the previous coloring situation, "Account Status Check" corresponds to more than two business scenarios, such as "Payment Transaction Business" and "Loan Business". Then, according to the corresponding labels "100" and "110" (assuming the label for the loan business is 110), trace the "Payment Transaction Business" and "Loan Business" services, query all relevant data based on the labels, and sort the data in ascending order according to the time when the service node calls the data.

[0139] Similarly, on the front-end device, the call links of the "Payment Transaction Business" and "Loan Business" services and the identification information of the corresponding service nodes on the links will be displayed. Additionally, relevant time nodes and elapsed times will also be shown. The service node compares the current information with the error information, and on the front-end device, it can intuitively show which service node in which business scenario has a problem and which business scenarios are affected.

[0140] During the display stage as an example, the front-end device can display business information through operations such as aggregation mechanism, personalized customization, table form display, and topology form display.

[0141] The aggregation mechanism is to improve the query efficiency. The purpose is to reduce the consumption of traversing and querying one by one under the aggregation according to specific rules before querying, such as summarizing the data of one day according to the service dimension.

[0142] Personalized customization provides the front-end display ability for the display end to be arbitrarily dragged and set, and reuses the open-source software ability.

[0143] As an example, the front-end device can display business information in table form or topology form.

[0144] Figure 7 Schematic diagram of the table form for the front-end device to display business information. Such as Figure 7As shown, the data of multiple service nodes are neatly typeset from top to bottom on the display of the front-end device. Horizontally, from left to right, the following relevant information is shown in sequence: "Order of Service Node", "Corresponding Business Scenario Name", "Corresponding Time", "Time Consumed by this Service Node for Service", "Number of Transactions", "Transaction Success Rate", etc.

[0145] Figure 8 It is a schematic diagram of the topological form for the front-end device to display business information. As Figure 8 shown, the link of business invocation is shown on the front-end device, including the path from one service node to the next service node. Next to each service node, the transaction processing volume per second (Transaction Per Second), abbreviated as tps, the corresponding service time consumed in milliseconds (millisecond), abbreviated as ms, and the percentage of transaction success rate are also shown. For example, for service node a, the transaction processing volume per second is 367.64 tps, the service time consumed is 115.58 ms, and the transaction success rate of this service node is 100%.

[0146] Figure 9 It is a schematic diagram of a service node provided by an embodiment of the present application. As Figure 9 shown, the service node 900 may include: a first receiving module 901, an obtaining module 902, and a first sending module 903.

[0147] The service node 900 can be used to implement Figure 3 the schematic flowchart applied in the monitoring method of the business system in the shown embodiment. Among them, the first receiving module 901 can be used to execute the step of S310, the obtaining module 902 can be used to execute the step of S320, and the first sending module 903 can be used to execute the steps of S330 and S340.

[0148] Figure 10 It is a schematic diagram of a database server provided by an embodiment of the present application. As Figure 10 shown, the database server 1000 may include: a second receiving module 1001, a storage module 1002, and a second sending module 1003.

[0149] The database server 1000 can be used to implement Figure 5 the schematic flowchart of the monitoring method of the business system in the shown embodiment. Among them, the second receiving module 1001 can be used to execute the step of S510, the storage module 1002 can be used to execute the step of S520, and the second sending module 1003 can be used to execute the step of S530.

[0150] Figure 11Schematic diagram of a front-end device provided by an embodiment of the present application, as Figure 11 shown. The front-end device 1100 may include: a third receiving module 1101 and a display module 1102.

[0151] The front-end device 1100 may be used to implement Figure 6 the schematic flowchart of the monitoring method of the business system shown in the embodiment. Among them, the third receiving module 1101 may be used to execute the step of S610, and the display module 1102 may be used to execute the step of S620.

[0152] Figure 12 Schematic diagram of a computing device provided by an embodiment of the present application, as Figure 12 shown. The computing device 1200 includes: a processor 1201 and an interface circuit 1202. The processor 1201 and the interface circuit 1202 are coupled to each other.

[0153] It can be understood that the processor 1201 collects and records data, and the interface circuit 1202 may be a transceiver or an input / output interface. Optionally, the computing device 1200 may further include a memory 1203, which is used to store the instructions executed by the processor 1201 or the input data required for the processor 1201 to run the instructions or the data generated after the processor 1201 runs the instructions.

[0154] The computing device 1200 may be a service node, a database server, or a front-end device. When the computing device 1200 is a service node, it may be used to implement Figure 3 the method shown; when the computing device 1200 is a database server, it may be used to implement Figure 5 the method shown; when the computing device 1200 is a front-end device, it may be used to implement Figure 6 the method shown.

[0155] It can be understood that the processor in the embodiments of the present application may be a central processing unit, or other general-purpose processors, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0156] The method steps in the embodiments of the present application can be implemented in a hardware manner or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a removable hard disk, a compact disc read-only memory (CD-ROM), or any other form of storage medium well-known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). Additionally, the ASIC can be located in a network device or a terminal device. Of course, the processor and the storage medium can also exist as discrete components in the network device or the terminal device.

[0157] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server or a data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it can also be an optical medium, such as a digital video disc; or it can be a semiconductor medium, such as a solid-state drive.

[0158] In various embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be cross-referenced. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships. The term "plurality" herein refers to two or more. The term "and / or" herein merely describes the associated relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " herein generally represents an "or" relationship between the preceding and following associated objects; in a formula, the character " / " represents a "division" relationship between the preceding and following associated objects.

[0159] It can be understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application.

[0160] It can be understood that in the embodiments of the present application, the magnitudes of the serial numbers of the above processes do not mean the sequence of execution. The execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. Those skilled in the art will readily think of other implementation manners of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and embodiments are only regarded as exemplary, and the true scope of the present application is pointed out by the claims.

[0161] It should be understood that the present application is not limited to the exact structure already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A monitoring method for a service system, characterized in that, Applied to a service node, including: The service node receives first information for requesting to invoke a service on the service node; The service node obtains the current business scenario information of the service according to the first information; The service node periodically sends service information to the database server, where the service information includes the identification information of the service node, the current business scenario information, the time information when the service node provides the service, and the duration information of the service node providing the service; wherein, the database server is used to send the service information to the front-end device in response to the service information request information sent by the front-end device; The service node obtains the current business scenario information of the service according to the first information, including: When the first information is information sent by the upstream service node of the service node based on the upstream service and the upstream service's business scenario information is included in the first information, the service node determines the upstream service's business scenario information as the current business scenario information; When the first information is information sent by the upstream service node of the service node based on the upstream service, the upstream service's business scenario information is not included in the first information, and the service node has set business scenario information for the service, the service node determines the business scenario information set for the service in the service node as the current business scenario information; When the first information is information sent by the front-end device and the service node has set business scenario information for the service, the service node determines the business scenario information set for the service in the service node as the current business scenario information.

2. The method according to claim 1, characterized in that, The method further includes: The service node sends second information to the downstream service node based on the first information, where the second information is used to request to invoke a downstream service on the downstream service node, and the second information includes the current business scenario information.

3. A monitoring method for a service system, characterized in that, Applied to a database server, including: The database server receives service information request information from the front-end device; The database server receives service information from the service node, where the service information includes the identification information of the service node, business scenario information, and key information, and the key information includes the time when the service node obtains the business scenario information and the duration of providing services for the business corresponding to the business scenario information; The database server stores the service information; The database server sends the service information to the front-end device in response to the service information request information; When the service scenario information is the information sent by the upstream service node of the service node based on the upstream service according to the first information, and the first information contains the service scenario information of the upstream service, the service node determines the service scenario information of the upstream service as the current service scenario information; when the first information is the information sent by the upstream service node of the service node based on the upstream service, the first information does not contain the service scenario information of the upstream service, and the service scenario information is set for the service in the service node, the service node determines the service scenario information set for the service in the service node as the current service scenario information; when the first information is the information sent by the front-end device, and the service scenario information is set for the service in the service node, the service node determines the service scenario information set for the service in the service node as the current service scenario information.

4. A monitoring method for service information, characterized in that, Applied to a front-end device, including: The front-end device sends service information request information to the database server; The front-end device receives service information from the database server, and the service information includes the identification information of the service node, the service scenario information, and the key information. The key information includes the time when the service node obtains the service scenario information and the duration of providing services for the service corresponding to the service scenario information; The front-end device displays the service information; When the service scenario information is the information sent by the upstream service node of the service node based on the upstream service according to the first information, and the first information contains the service scenario information of the upstream service, the service node determines the service scenario information of the upstream service as the current service scenario information; when the first information is the information sent by the upstream service node of the service node based on the upstream service, the first information does not contain the service scenario information of the upstream service, and the service scenario information is set for the service in the service node, the service node determines the service scenario information set for the service in the service node as the current service scenario information; when the first information is the information sent by the front-end device, and the service scenario information is set for the service in the service node, the service node determines the service scenario information set for the service in the service node as the current service scenario information.

5. A service node, characterized in that, Including: A first receiving module, configured to receive first information, where the first information is used to request to invoke the service on the service node; An obtaining module, configured to obtain the current service scenario information of the service according to the first information; A first sending module, configured to periodically send service information to the database server, where the service information includes the identification information of the service node, the current service scenario information, the time information of the service node providing the service, and the duration information of the service node providing the service; wherein, the database server is configured to send the service information to the front-end device in response to the service information request information sent by the front-end device. The obtaining module is specifically configured to: when the first information is the information sent by the upstream service node of the service node based on the upstream service, and the first information contains the business scenario information of the upstream service, the service node determines the business scenario information of the upstream service as the current business scenario information; when the first information is the information sent by the upstream service node of the service node based on the upstream service, the first information does not contain the business scenario information of the upstream service, and the service node has set the business scenario information for the service, the service node determines the business scenario information set for the service in the service node as the current business scenario information; when the first information is the information sent by the front-end device, and the service node has set the business scenario information for the service, the service node determines the business scenario information set for the service in the service node as the current business scenario information.

6. A database server, characterized in that, including: A second receiving module, configured to receive business information from the service node, where the business information contains the identification information, business scenario information, and key information of the service node, and the key information includes the time when the service node obtains the business scenario information and the duration of providing services for the business corresponding to the business scenario information; The business scenario information is obtained by the service node according to the first information for the upstream service node of the service node based on the information sent by the upstream service. When the first information contains the business scenario information of the upstream service, the service node determines the business scenario information of the upstream service as the current business scenario information; when the first information is the information sent by the upstream service node of the service node based on the upstream service, the first information does not contain the business scenario information of the upstream service, and the service node has set the business scenario information for the service, the service node determines the business scenario information set for the service in the service node as the current business scenario information; when the first information is the information sent by the front-end device, and the service node has set the business scenario information for the service, the service node determines the business scenario information set for the service in the service node as the current business scenario information A storage module, configured to store the business information; A second sending module, configured to send the business information to the front-end device by the database server in response to the business information request information; The second receiving module is further configured to receive business information request information from the front-end device.

7. A front-end device, characterized in that, including: A third sending module, configured to send business information request information to the database server A third receiving module: configured to receive business information from the database server, where the business information contains the identification information, business scenario information, and key information of the service node, and the key information includes the time when the service node obtains the business scenario information and the duration of providing services for the business corresponding to the business scenario information; When the service scenario information is the information sent by the upstream service node of the service node based on the upstream service according to the first information, and the first information contains the service scenario information of the upstream service, the service node determines the service scenario information of the upstream service as the current service scenario information; when the first information is the information sent by the upstream service node of the service node based on the upstream service, the first information does not contain the service scenario information of the upstream service, and the service scenario information is set for the service in the service node, the service node determines the service scenario information set for the service in the service node as the current service scenario information; when the first information is the information sent by the front-end device, and the service scenario information is set for the service in the service node, the service node determines the service scenario information set for the service in the service node as the current service scenario information A display module for displaying the service information.

8. A computing device, characterized in that, It includes a memory and a processor coupled to the memory; The memory is used for storing program instructions; The processor is used for executing the program instructions to implement the method according to any one of claims 1 to 4.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program code for computer execution, and the program code includes instructions for implementing the method according to any one of claims 1 to 4.

10. A computer program product, characterized in that, It includes a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 4.

Images