CN113220540A - Service management method, device, computer equipment and storage medium - Google Patents
Service management method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN113220540A CN113220540A CN202110631388.5A CN202110631388A CN113220540A CN 113220540 A CN113220540 A CN 113220540A CN 202110631388 A CN202110631388 A CN 202110631388A CN 113220540 A CN113220540 A CN 113220540A
- Authority
- CN
- China
- Prior art keywords
- service
- component
- exception handling
- information
- service node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/327—Alarm or error message display
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Computing Systems (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to a service management method, a service management device, computer equipment and a storage medium. The method comprises the following steps: receiving component related information of each business component in a business component set; determining a service component with an abnormal state from the service component set according to the relevant information of the component, and taking the service component as an abnormal service component; determining a target service node corresponding to the abnormal service component according to the corresponding relation between the component and the service node, wherein the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to transaction functions, and one or more service components with service function cooperation relation form the service node; and acquiring an exception handling message corresponding to the exception service component, and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message. The method can improve the stability of service management.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a service management method, an apparatus, a computer device, and a storage medium.
Background
With the development of computer application technology, the importance of enterprises to data is increasing, so the demand of business data processing is increasing, and the demand of developing or repairing the business management data is also increasing.
However, there may be situations where there is a problem with the service data or the data system, for example, there is an error in the output data. In the conventional technology, when exception handling is performed on a system with problems, the stability of the whole system is easily affected, and the problem of poor stability exists.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a service management method, device, computer device and storage medium capable of improving stability of service management.
A method of traffic management, the method comprising: receiving component related information of each business component in a business component set; determining a service component with an abnormal state from the service component set according to the component related information, and taking the service component as an abnormal service component; determining a target service node corresponding to the abnormal service component according to the corresponding relation between the component and the service node, wherein the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to transaction functions, and one or more service components with service function cooperation relation form the service node; and acquiring an exception handling message corresponding to the exception service component, and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message.
In one embodiment, the determining, according to the correspondence between the component and the service node, a target service node corresponding to the abnormal service component includes: acquiring a preset subscription information set, wherein the subscription information in the subscription information set comprises service component information subscribed by a service node, and the service component information subscribed by the service node is information forming a service component of the service node; and determining a service node subscribing the information of the abnormal service component in the subscription information set as a target service node corresponding to the abnormal service component. In one of the embodiments, the first and second electrodes are,
in one embodiment, the component related information includes a component log information set, and the determining a service component with an abnormal state from the service component set according to the component log information includes, as an abnormal service component: arranging the component log information sets to obtain a log information sequence, and acquiring a log time interval between each two adjacent pieces of log information in the log information sequence; and when at least one log time interval is larger than a time interval threshold, determining that the business component is an abnormal business component.
In one embodiment, the obtaining the exception handling message corresponding to the exception service component and sending the exception handling file to the target service node includes: determining a log information group with a log time interval larger than a time interval threshold value, and determining the missing log generation time of the missing log information based on the generation time of the log information in the log information group; and generating an exception handling message corresponding to the missing log rereading instruction based on the missing log generation time, wherein the exception handling message carries the missing log generation time, and sending the exception handling file to the target service node.
In one embodiment, the method further comprises: receiving a service document sent by a service terminal; determining missing service data of a service node corresponding to the service terminal based on the service data corresponding to the service receipt; in a storage unit, acquiring the missing service data; and sending the missing service data to the target service node so that the target service node completes node repair by using the missing service data.
In one embodiment, the obtaining the exception handling message corresponding to the exception service component and sending the exception handling message to the target service node include: displaying abnormal state prompt information corresponding to the abnormal service component; responding to the exception handling operation aiming at the exception state prompt message, acquiring a target exception handling strategy selected by the exception handling operation, acquiring an exception handling message corresponding to the target exception handling strategy, and sending the exception handling message to the target service node.
In one embodiment, the abnormal state prompt message comprises abnormal state description information; the exception handling operation comprises a description information editing operation and an exception handling strategy selecting operation; the obtaining of the target exception handling policy selected by the exception handling operation in response to the exception handling operation for the exception state hint information comprises: responding to description information editing operation aiming at the abnormal state description information, and displaying the edited abnormal description information, wherein the edited abnormal description information is the abnormal state description information edited based on the description information editing operation; in response to an information confirmation operation for the edited exception description information, acquiring a candidate exception handling policy based on the edited exception description information; and responding to the exception handling strategy selection operation, and taking the candidate exception strategy selected by the exception handling strategy selection operation as a target exception handling strategy.
A traffic management apparatus, the apparatus comprising: the component related information receiving module is used for receiving component related information of each business component in the business component set; an abnormal business component determining module, configured to determine a business component with an abnormal state from the business component set according to the component related information, as an abnormal business component; a target service node determining module, configured to determine a target service node corresponding to the abnormal service component according to a corresponding relationship between the component and the service node, where the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to a transaction function, and one or more service components having a service function cooperation relationship form a service node; and the target service node sending module is used for acquiring the exception handling message corresponding to the exception service component and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message.
In one embodiment, the target service node determining module is configured to obtain a pre-configured subscription information set, where the subscription information in the subscription information set includes service component information subscribed by a service node, and the service component information subscribed by the service node is information of a service component forming the service node; and determining a service node subscribing the information of the abnormal service component in the subscription information set as a target service node corresponding to the abnormal service component.
In one embodiment, the abnormal service component determining module is configured to arrange the component log information sets to obtain a log information sequence, and obtain a log time interval between each two adjacent pieces of log information in the log information sequence; and when at least one log time interval is larger than a time interval threshold, determining that the business component is an abnormal business component.
In one embodiment, the abnormal service component determination module is configured to determine a log information group with a log time interval greater than a time interval threshold, and determine a missing log generation time of the missing log information based on a generation time of log information in the log information group; and generating an exception handling message corresponding to the missing log rereading instruction based on the missing log generation time, wherein the exception handling message carries the missing log generation time, and sending the exception handling file to the target service node.
In one embodiment, the apparatus comprises: the business document receiving module is used for receiving the business document sent by the business terminal; the missing service data determining module is used for determining missing service data of a service node corresponding to the service terminal based on the service data corresponding to the service bill; a missing service data acquisition module, configured to acquire the missing service data in a storage unit; and the missing service data sending module is used for sending the missing service data to the target service node so that the target service node completes node repair by using the missing service data.
In one embodiment, the exception handling message sending module is configured to show exception status prompt information corresponding to the exception service component; responding to the exception handling operation aiming at the exception state prompt message, acquiring a target exception handling strategy selected by the exception handling operation, acquiring an exception handling message corresponding to the target exception handling strategy, and sending the exception handling message to the target service node.
In one embodiment, the exception handling message sending module is configured to display edited exception description information in response to a description information editing operation for the exception description information, where the edited exception description information is the exception description information edited based on the description information editing operation; in response to an information confirmation operation for the edited exception description information, acquiring a candidate exception handling policy based on the edited exception description information; and responding to the exception handling strategy selection operation, and taking the candidate exception strategy selected by the exception handling strategy selection operation as a target exception handling strategy.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program: receiving component related information of each business component in a business component set; determining a service component with an abnormal state from the service component set according to the component related information, and taking the service component as an abnormal service component; determining a target service node corresponding to the abnormal service component according to the corresponding relation between the component and the service node, wherein the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to transaction functions, and one or more service components with service function cooperation relation form the service node; and acquiring an exception handling message corresponding to the exception service component, and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of: receiving component related information of each business component in a business component set; determining a service component with an abnormal state from the service component set according to the component related information, and taking the service component as an abnormal service component; determining a target service node corresponding to the abnormal service component according to the corresponding relation between the component and the service node, wherein the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to transaction functions, and one or more service components with service function cooperation relation form the service node; and acquiring an exception handling message corresponding to the exception service component, and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message.
The service management method, the service management device, the computer equipment and the storage medium receive the component related information of each service component in the service component set; determining a service component with an abnormal state from the service component set according to the relevant information of the component, and taking the service component as an abnormal service component; determining a target service node corresponding to the abnormal service component according to the corresponding relation between the component and the service node, wherein the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to transaction functions, and one or more service components with service function cooperation relation form the service node; and acquiring an exception handling message corresponding to the exception service component, and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message. The method and the device can achieve that under the condition that the target service node is determined, the exception processing is completed on the service component in the target service node by sending the exception processing message to the target service node, reduce the influence on other transaction nodes and improve the stability of service management.
Drawings
FIG. 1 is a diagram of an application environment of a method for service management in one embodiment;
FIG. 2 is a flow diagram illustrating a method for service management in one embodiment;
FIG. 3 is a flow chart illustrating a method for service management in another embodiment;
FIG. 4 is a flow chart illustrating a method for service management in another embodiment;
FIG. 5 is a flow chart illustrating a method for service management in another embodiment;
FIG. 6 is a flow chart illustrating a method for service management in another embodiment;
FIG. 7 is a flow chart illustrating a method for service management in another embodiment;
FIG. 8 is a flow chart illustrating a method for service management in another embodiment;
FIG. 9 is a diagram illustrating an interface of an operation and maintenance management platform according to an embodiment;
FIG. 10 is a block diagram of a traffic management device in one embodiment;
FIG. 11 is a diagram illustrating an internal structure of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The service management method provided by the application can be applied to the application environment shown in fig. 1, and is particularly applied to a service management system. The service management system comprises an operation and maintenance server 102 and a service server 104, wherein the operation and maintenance server 102 communicates with the service server 104 through a network. The operation and maintenance server 102 executes a service management method, and specifically, the operation and maintenance server 102 receives component related information of each service component in a service component set sent by the service server 104; determining a service component with an abnormal state from the service component set according to the relevant information of the component, and taking the service component as an abnormal service component; determining a target service node corresponding to the abnormal service component according to the corresponding relation between the component and the service node, wherein the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to transaction functions, and one or more service components with service function cooperation relation form the service node; and acquiring an exception handling message corresponding to the exception service component, and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message. The operation and maintenance server 102 and the service server 104 may be implemented by separate servers or a server cluster composed of a plurality of servers. It is understood that the service server 104 may be replaced by a terminal, which may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices.
In one embodiment, as shown in fig. 2, a service management method is provided, which is described by taking the application of the method to the server in fig. 1 as an example, and includes the following steps:
step 202, receiving component related information of each business component in the business component set.
The service component refers to a software program capable of completing a certain service function. For example, in a security system, a trading engine component is responsible for processing trading requests for a security trade. The component-related information refers to information related to a state of a component, and for example, the component-related information is operation state information of the component.
Specifically, the operation status of the business component can be determined by the component-related information received by the server.
In one embodiment, the server receives the component related information of each business component in the business component set through the information receiving module, and displays the component related information on a platform interface connected with the server in a visual form.
And step 204, determining the service component with abnormal state from the service component set according to the relevant information of the component, and taking the service component as the abnormal service component.
The abnormal business component refers to a business component with an abnormal running state.
Specifically, after receiving the component related information of each service component, the server determines the service component with an abnormal state by judging the running state information in the component related information. For example, if the running state information in the component related information indicates that a destination network address set in the gateway is abnormal, the gateway component is an abnormal service component.
And step 206, determining a target service node corresponding to the abnormal service component according to the corresponding relation between the component and the service node, wherein the target service node is obtained by screening from the service node set, the service nodes in the service node set are divided according to transaction functions, and one or more service components with service function cooperation relation form the service node.
The service node refers to a node formed by one or more service components for realizing a certain service function. For example, in a securities system, a business node is a system report service node, and the node needs to be completed by cooperation of a commodity information acquisition component, a report information sending component and other components.
Specifically, a corresponding relationship exists between the service components and the service nodes, the corresponding service nodes can be determined through the service components, and after the server determines the abnormal service components, the corresponding target service nodes can be screened and determined from the service node set through the abnormal service components.
And 208, acquiring an exception handling message corresponding to the exception service component, and sending the exception handling message to the target service node, so that the target service node performs exception handling according to the exception handling message.
The exception handling message is a message capable of performing exception handling on the exception service component. The message may be a processing file for performing exception processing on the abnormal service component, or may be data for performing exception processing on the abnormal service component.
Specifically, after determining a target service node corresponding to an abnormal service component, the server obtains an abnormal processing message corresponding to the abnormal service component from an abnormal processing message set stored in the server through a corresponding relationship between the abnormal service component and the abnormal processing message, and sends the abnormal processing message to the target service node corresponding to the abnormal service component, so that the target service node performs abnormal processing according to the abnormal processing message.
In the service management method, the component related information of each service component in the service component set is received; determining a service component with an abnormal state from the service component set according to the relevant information of the component, and taking the service component as an abnormal service component; determining a target service node corresponding to the abnormal service component according to the corresponding relation between the component and the service node, wherein the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to transaction functions, and one or more service components with service function cooperation relation form the service node; and acquiring an exception handling message corresponding to the exception service component, and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message. The method and the device can achieve that under the condition of determining the target service node, the exception processing is completed on the service component in the target service node by sending the exception processing message to the target service node, thereby ensuring that other service nodes are not affected and improving the stability of service management.
In an embodiment, as shown in fig. 3, determining a target service node corresponding to an abnormal service component according to a correspondence between the component and the service node includes:
step 302, a pre-configured subscription information set is obtained, the subscription information in the subscription information set includes service component information subscribed by a service node, and the service component information subscribed by the service node is information forming a service component of the service node.
Specifically, the server stores a subscription information set, where the subscription information set is subscription information configured in advance according to a correspondence between the service node and the service component, and the subscription information is service component information subscribed by the service node.
And 304, determining a service node subscribing the information of the abnormal service component in the subscription information set as a target service node corresponding to the abnormal service component.
Specifically, after the server acquires the subscription information set, the service node that acquires the information of the subscription abnormal service component is used as the target service node corresponding to the abnormal service component.
In this embodiment, by acquiring a pre-configured subscription information set, a service node subscribing to information of an abnormal service component is determined in the subscription information set, and the service node is used as a target service node corresponding to the abnormal service component, so that a purpose of accurately determining the target service node can be achieved.
In one embodiment, as shown in fig. 4, the component related information includes a component log information set, and the determining a service component with an abnormal state from the service component set according to the component log information includes, as an abnormal service component:
step 402, arranging the component log information sets to obtain a log information sequence, and obtaining a log time interval between each two adjacent pieces of log information in the log information sequence.
The component log information refers to log information generated in the operation process of the service component.
Specifically, the business component generates component log information during operation, and time intervals exist among the component log information.
In one embodiment, a server receives a plurality of component log information, the plurality of component log information form a component log information set, the generation time of each component log information in the component log information set is different, the component log information sets are arranged according to the different generation times to obtain a log information sequence, and the generation time difference value between adjacent log information is calculated according to the log information sequence to obtain a log time interval.
And step 404, when at least one log time interval is larger than a time interval threshold, determining that the service component is an abnormal service component.
The time interval threshold is a critical value of the time interval, and if the time interval threshold is larger than or equal to the critical value, the time interval is considered to be abnormal, and if the time interval threshold is smaller than the critical value, the time interval is considered to be normal.
Specifically, after the server obtains the log time interval between each adjacent log information in the log information sequence, when at least one log time interval is greater than a time interval threshold, the service component is determined to be an abnormal service component.
In this embodiment, the log information sequence is obtained by arranging the component log information sets, the log time interval between each two adjacent pieces of log information in the log information sequence is obtained, and when at least one log time interval is greater than the time interval threshold, the service component is determined to be an abnormal service component, so that the purpose of accurately determining the abnormal service component can be achieved.
In an embodiment, as shown in fig. 5, acquiring an exception handling message corresponding to an exception service component, and sending an exception handling file to a target service node includes:
step 502, determining a log information group with a log time interval larger than a time interval threshold, and determining the missing log generation time of the missing log information based on the generation time of the log information in the log information group.
The log information group refers to two or more log information corresponding to the service component.
Specifically, log information exists in the log information group, the log information includes generation time of the log information, when the generation time between the log information is larger than a time interval threshold value, missing log information between the log information is confirmed, and the missing log generation time of the missing log information is determined through the time interval between other log information. For example, the log information in the log information group is generated at 10:01:00, 10:01:01, 10:01:03, and 10:01:05 times, respectively, with a time interval threshold of 1 second, wherein the time interval between the fourth log information and the fifth log information is 2 seconds, and if it exceeds 1 second which is the time interval threshold, it is considered that there is a missing log between the fourth log information and the fifth log information.
And step 504, generating an exception handling message corresponding to the missing log rereading instruction based on the missing log generation time, wherein the exception handling message carries the missing log generation time, and sending the exception handling message to the target service node.
The missing log rereading instruction refers to an instruction capable of rereading the missing log.
Specifically, after determining the missing log generation time of the missing log information, the server generates an exception handling message corresponding to the missing log rereading instruction based on the missing log generation time, and sends the exception handling message to the target service node according to the missing log generation time carried in the exception handling message. And re-reading the log of the target service node at the missing log generation time through the exception handling message.
In this embodiment, by determining a log information group with a log time interval larger than a time interval threshold, determining missing log generation time of missing log information based on generation time of log information in the log information group, and generating an exception handling message corresponding to a missing log rereading instruction based on the missing log generation time, a missing log of a target service node can be acquired, so that a defect that log information acquired by the target service node is incomplete due to an exception is repaired.
In one embodiment, as shown in fig. 6, the service management method further includes:
step 602, receiving a service bill sent by a service terminal.
The business document refers to a document capable of developing a certain business. For example, in a security system, a customer makes a transaction document for placing an order.
Specifically, the business terminal completes generation of the business document through the document placement guide and sends the business document to the home terminal server, and correspondingly, the home terminal server receives the business document sent by the business terminal through the data receiving module.
Step 604, determining missing service data of a service node corresponding to the service terminal based on the service data corresponding to the service receipt.
The service data refers to metadata corresponding to the service document, and the metadata can describe attributes, functions, acquisition rights and the like of each data in the service document. For example, in a security system, a business document is a stock transaction document, and business data corresponding to the transaction document includes an account name or a number of bought stocks.
Specifically, after receiving a service document sent by a service terminal, the server compares service data corresponding to the service document with reference service data stored in the server and corresponding to the service document of the type to obtain service data which exists in the reference service data but does not exist in the service data corresponding to the service document, and determines the part of service data as missing service data of a service node corresponding to the service terminal.
Step 606, obtaining the missing service data in the storage unit.
Specifically, the server is provided with a storage unit in a preset storage area, and the missing service data can be acquired in the storage unit.
In one embodiment, after determining the missing service data of the service node corresponding to the service terminal, the server triggers a data reading operation in the storage unit, and obtains the missing service data from the storage unit through the reading operation.
Specifically, after acquiring the missing service data, the server sends the missing service data to the target service node, and after receiving the missing service data, the target service node triggers a repair instruction for the target service node according to the corresponding relationship between the missing service data and the repair instruction, and completes the repair of the target service node by using the repair instruction. For example, in a security system, missing service data is service data described as a purchase amount, when a server receives the service data, the service data is sent to a trading node, and when the trading node receives the service data, a data missing repair instruction of the trading node is triggered, and the missing data is added to the trading node, so that the trading node can acquire the service data described as the purchase amount when acquiring the service data.
In this embodiment, by receiving a service document sent by a service terminal, missing service data corresponding to a service node is determined based on service data corresponding to the service document, the missing service data is obtained in a storage unit, and the missing service data is sent to a target service node, so that the target service node completes node repair by using the missing service data, and the purpose of completing repair of the target service node by determining the missing service data can be achieved.
In an embodiment, as shown in fig. 7, acquiring an exception handling message corresponding to an exception service component, and sending the exception handling message to a target service node includes:
step 702, displaying the abnormal state prompt information corresponding to the abnormal service component.
Specifically, after the server determines the abnormal state prompt information, the abnormal state prompt information is displayed on a display platform connected with the server in a visual mode. For example, in an operation and maintenance management platform in a security system, after a server connected to the operation and maintenance management platform receives an abnormal state prompt message corresponding to an abnormal service component, the abnormal state prompt message is visually displayed on the operation and maintenance management platform. For example, an abnormal state prompt message such as "the business component a has an abnormality that the business data cannot be acquired" is displayed on the operation and maintenance management platform.
Step 704, in response to the exception handling operation for the exception state prompting information, obtaining a target exception handling policy selected by the exception handling operation, obtaining an exception handling message corresponding to the target exception handling policy, and sending the exception handling message to the target service node.
The exception handling operation refers to an operation performed on the exception state prompting information. For example, the abnormal state prompt message indicates that "the service component B is abnormal, please select an abnormal processing mode, mode 1: XXX; mode 2: XXX ", the exception handling operation may select either mode 1 or mode 2. The target exception handling policy refers to a handling policy corresponding to an exception handling operation. For example, when the above exception handling operation selects mode 1, the handling policy corresponding to mode 1 is the target exception handling policy. The exception handling message refers to a handling message corresponding to the target exception handling policy, for example, if the target exception handling policy is the handling policy of the selection mode 1, the exception handling message is a handling message generated after the operation of the selection mode 1 is selected.
Specifically, the server obtains a target exception handling policy selected by exception handling operation by displaying exception state prompt information corresponding to the exception service component and exception handling operation on the exception state prompt information of the message, obtains an exception handling message corresponding to the target exception handling policy by the target exception handling policy, and sends the exception handling message to the target service node. It can be understood that each exception handling operation corresponds to a different target exception handling policy, and the different target exception handling policies correspond to different exception handling messages, so that the exception handling messages can be sent to the target service node through the exception handling operation of the exception status prompt message of the message.
In this embodiment, the abnormal state prompt information corresponding to the abnormal service component is displayed through the display platform corresponding to the server, the target abnormal processing strategy selected by the abnormal processing operation is acquired in response to the abnormal processing operation aiming at the abnormal state prompt information, the abnormal processing message corresponding to the target abnormal processing strategy is acquired, and the abnormal processing message is sent to the target service node, so that the target service node can complete the abnormal repair through the abnormal processing message through the intuitive abnormal processing operation.
In one embodiment, as shown in FIG. 8, the exception status prompting information includes exception status description information; the exception handling operation comprises a description information editing operation and an exception handling strategy selecting operation; in response to the exception handling operation for the exception state hint information, obtaining the target exception handling policy selected by the exception handling operation comprises:
step 802, in response to the description information editing operation for the abnormal state description information, displaying the edited abnormal description information, where the edited abnormal description information is the abnormal state description information edited based on the description information editing operation.
The abnormal state description information refers to descriptive information of an abnormal state. The description information editing operation refers to an editing operation on the abnormal state description information. The exception handling policy selection operation refers to a selection operation of an exception handling policy.
Specifically, the display platform corresponding to the server displays the abnormal state description information, and in order to enable the abnormal state description information to be more accurate and meet the maintenance purpose, the abnormal state description information may be edited. And receiving description information editing operation on the abnormal state description information, responding to the description information editing operation, and displaying the edited abnormal description information.
And step 804, responding to the information confirmation operation aiming at the edited abnormal description information, and acquiring a candidate abnormal processing strategy based on the edited abnormal description information.
Specifically, an information confirmation operation of the edited exception description information is acquired on the displayed edited exception description information, and in response to the information confirmation operation, a candidate exception handling policy is acquired according to the edited exception description information. The exception handling policy may be a combination of keywords in the exception description information. For example, the exception handling policy is "Business component C restart".
And step 806, responding to the exception handling strategy selection operation, and taking the candidate exception strategy selected by the exception handling strategy selection operation as a target exception handling strategy.
Specifically, after receiving an exception handling policy selection operation, the server responds to the exception handling policy selection operation and takes the selected candidate exception policy as a target exception handling policy.
In this embodiment, the edited exception description information is displayed in response to the description information editing operation for the exception state description information, a candidate exception handling policy is acquired based on the edited exception description information in response to the information confirmation operation for the edited exception description information, and the candidate exception policy selected by the exception handling policy selection operation is used as the target exception handling policy in response to the exception handling policy selection operation, so that the purpose of accurately obtaining the target exception handling policy can be achieved.
In one embodiment, the business management in the operation and maintenance management system in the securities system is taken as an example. The operation and maintenance management system is used for service management by taking transaction nodes as units, the transaction nodes are nodes capable of independently completing transaction services, the transaction nodes can be composed of a plurality of transaction components, and each transaction component or the transaction nodes composed of the transaction components can realize a transaction function. For example, the transaction components include a transaction gateway component GW, a transaction engine component TE, and a system report service component ORS. The functions realized by the transaction component can be realized by one server or a plurality of servers; likewise, the functions of multiple transaction components may be implemented by a single server. The operation and maintenance management platform stores and maintains the relationship among all transaction nodes and the functions of all transaction components. The operation and maintenance management platform sends the management file to the trading nodes, and can manage part or all of the trading nodes, for example: the management file can realize the starting and stopping of the transaction node, the receiving and sending of instructions and the like. Including files of different formats and content.
In one embodiment, the trading nodes are managed by using a uniform operation and maintenance management platform, and data is interacted between the operation and maintenance management platform and the trading nodes in a file and subscription message mode. When the operation and maintenance platform is deployed, the subscription information of each transaction node is configured. When the file is required to be sent, the operation and maintenance platform obtains the preset subscription information, and searches a target transaction node required to receive the file according to the corresponding transaction node in the subscription information.
In one embodiment, a server corresponding to each transaction node deploys a proxy server for monitoring, and the proxy server monitors the status of the transaction node, for example: whether the monitoring process exists or not, whether the log generated by the monitoring process is abnormal or not and whether the monitoring process normally outputs heartbeat information or not. The proxy server writes the acquired data into the database, and the operation and maintenance platform polls the data of the database and judges the state of each transaction node.
In one embodiment, the server determines the state of the transaction node according to the data collected by the proxy server, and sends the state of the transaction node to the operation and maintenance management platform. When the starting of part of the transaction nodes is abnormal, the operation and maintenance platform can send a restart instruction to the corresponding transaction nodes through message service so as to restart the transaction nodes. If the transaction node has data errors, the operation and maintenance management platform can modify the data on the corresponding transaction node in real time by sending an instruction. For example, when a certain transaction node has business data missing, the operation and maintenance platform determines the missing data and sends a data re-reading instruction to the corresponding transaction node according to the generation time of the missing data, so that the transaction node regenerates the business data at the corresponding time. Because the file and the instruction are sent to a certain trading node or some trading nodes, and other trading nodes are not influenced by the file and the instruction, other nodes can normally operate. As shown in fig. 9, the operation and maintenance platform displays the state of each managed transaction node based on the data collected by the proxy server, and may also specifically display the state of the transaction component corresponding to each node. When an example corresponding to a certain transaction component is abnormal, a box corresponding to the example is displayed in dark color, the number of the abnormal example in all the examples is displayed in proportion, and the like.
In one embodiment, when determining that a certain transaction component of a certain transaction node is abnormal, the operation and maintenance platform determines a coping file corresponding to the abnormality of the transaction component, and sends the coping file to the transaction node to trigger the corresponding transaction node to process the abnormality of the corresponding transaction component. While the normal operation of other transaction components is not affected by the exception instance. In addition, because the other transaction nodes and the transaction node with the abnormal transaction are in mutually independent relationship, the process of processing the abnormal transaction node does not influence other normal operation.
It should be understood that although the various steps in the flow charts of fig. 2-8 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-8 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 10, there is provided a traffic management apparatus 1000, including: a component related information receiving module 1002, an abnormal service component determining module 1004, a target service node determining module 1006 and an exception handling message sending module 1008, wherein: a component related information receiving module 1002, configured to receive component related information of each service component in a service component set; an abnormal business component determining module 1004, configured to determine a business component with an abnormal state from the business component set according to the component related information, as an abnormal business component; a target service node determining module 1006, configured to determine a target service node corresponding to the abnormal service component according to a corresponding relationship between the component and the service node, where the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to a transaction function, and one or more service components having a service function cooperation relationship form a service node; the exception handling message sending module 1008 is configured to obtain an exception handling message corresponding to the exception service component, and send the exception handling message to the target service node, so that the target service node performs exception handling according to the exception handling message.
In one embodiment, the target service node determining module 1006 is configured to obtain a pre-configured subscription information set, where the subscription information in the subscription information set includes service component information subscribed by a service node, and the service component information subscribed by the service node is information of a service component forming the service node; and in the subscription information set, determining a service node subscribing the information of the abnormal service component as a target service node corresponding to the abnormal service component.
In an embodiment, the abnormal service component determining module 1004 is configured to arrange the component log information sets to obtain a log information sequence, and obtain a log time interval between each two adjacent pieces of log information in the log information sequence; and when at least one log time interval is larger than a time interval threshold, determining that the business component is an abnormal business component.
In one embodiment, the abnormal traffic component determining module 1004 is configured to determine a log information group with a log time interval greater than a time interval threshold, and determine a missing log generation time of the missing log information based on a generation time of log information in the log information group; and generating an exception handling message corresponding to the missing log rereading instruction based on the missing log generation time, wherein the exception handling message carries the missing log generation time, and sending the exception handling file to the target service node.
In one embodiment, an apparatus comprises: the business document receiving module is used for receiving the business document sent by the business terminal; the missing service data determining module is used for determining the missing service data of the service node corresponding to the service terminal based on the service data corresponding to the service document; the missing service data acquisition module is used for acquiring missing service data in the storage unit; and the missing service data sending module is used for sending the missing service data to the target service node so that the target service node completes node repair by using the missing service data.
In one embodiment, the exception handling message sending module 1008 is configured to show an exception status prompt message corresponding to the exception service component; and responding to the exception handling operation aiming at the exception state prompt message, acquiring a target exception handling strategy selected by the exception handling operation, acquiring an exception handling message corresponding to the target exception handling strategy, and sending the exception handling message to the target service node.
In one embodiment, the exception handling message sending module 1008 is configured to, in response to a description information editing operation for the exception state description information, display edited exception description information, where the edited exception description information is the exception state description information edited based on the description information editing operation; responding to an information confirmation operation aiming at the edited exception description information, and acquiring a candidate exception handling strategy based on the edited exception description information; and responding to the exception handling strategy selection operation, and taking the candidate exception strategy selected by the exception handling strategy selection operation as a target exception handling strategy.
For the specific definition of the service management device, reference may be made to the above definition of the service management method, which is not described herein again. The modules in the service management device can be implemented wholly or partially by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 11. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing business management data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a business management method.
Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.
In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for managing traffic, the method comprising:
receiving component related information of each business component in a business component set;
determining a service component with an abnormal state from the service component set according to the component related information, and taking the service component as an abnormal service component;
determining a target service node corresponding to the abnormal service component according to the corresponding relation between the component and the service node, wherein the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to transaction functions, and one or more service components with service function cooperation relation form the service node;
and acquiring an exception handling message corresponding to the exception service component, and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message.
2. The method of claim 1, wherein the determining the target service node corresponding to the abnormal service component according to the correspondence between the component and the service node comprises:
acquiring a preset subscription information set, wherein the subscription information in the subscription information set comprises service component information subscribed by a service node, and the service component information subscribed by the service node is information forming a service component of the service node;
and determining a service node subscribing the information of the abnormal service component in the subscription information set as a target service node corresponding to the abnormal service component.
3. The method according to claim 1, wherein the component-related information comprises a set of component log information, and the determining a business component with abnormal state from the set of business components according to the component log information comprises:
arranging the component log information sets to obtain a log information sequence, and acquiring a log time interval between each two adjacent pieces of log information in the log information sequence;
and when at least one log time interval is larger than a time interval threshold, determining that the business component is an abnormal business component.
4. The method according to claim 3, wherein the obtaining the exception handling message corresponding to the exception service component and sending the exception handling file to the target service node comprises:
determining a log information group with a log time interval larger than a time interval threshold value, and determining the missing log generation time of the missing log information based on the generation time of the log information in the log information group;
and generating an exception handling message corresponding to the missing log rereading instruction based on the missing log generation time, wherein the exception handling message carries the missing log generation time, and sending the exception handling file to the target service node.
5. The method of claim 1, further comprising:
receiving a service document sent by a service terminal;
determining missing service data of a service node corresponding to the service terminal based on the service data corresponding to the service receipt;
in a storage unit, acquiring the missing service data;
and sending the missing service data to the target service node so that the target service node completes node repair by using the missing service data.
6. The method according to claim 1, wherein the obtaining of the exception handling message corresponding to the exception service component and the sending of the exception handling message to the target service node comprises:
displaying abnormal state prompt information corresponding to the abnormal service component;
responding to the exception handling operation aiming at the exception state prompt message, acquiring a target exception handling strategy selected by the exception handling operation, acquiring an exception handling message corresponding to the target exception handling strategy, and sending the exception handling message to the target service node.
7. The method of claim 6, wherein the exception state prompting information includes exception state description information; the exception handling operation comprises a description information editing operation and an exception handling strategy selecting operation; the obtaining of the target exception handling policy selected by the exception handling operation in response to the exception handling operation for the exception state hint information comprises:
responding to description information editing operation aiming at the abnormal state description information, and displaying the edited abnormal description information, wherein the edited abnormal description information is the abnormal state description information edited based on the description information editing operation;
in response to an information confirmation operation for the edited exception description information, acquiring a candidate exception handling policy based on the edited exception description information;
and responding to the exception handling strategy selection operation, and taking the candidate exception strategy selected by the exception handling strategy selection operation as a target exception handling strategy.
8. A traffic management apparatus, characterized in that the apparatus comprises:
the component related information receiving module is used for receiving component related information of each business component in the business component set;
an abnormal business component determining module, configured to determine a business component with an abnormal state from the business component set according to the component related information, as an abnormal business component;
a target service node determining module, configured to determine a target service node corresponding to the abnormal service component according to a corresponding relationship between the component and the service node, where the target service node is obtained by screening from a service node set, the service nodes in the service node set are divided according to a transaction function, and one or more service components having a service function cooperation relationship form a service node;
and the exception handling message sending module is used for acquiring an exception handling message corresponding to the exception service component and sending the exception handling message to the target service node so that the target service node performs exception handling according to the exception handling message.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110631388.5A CN113220540B (en) | 2021-06-07 | 2021-06-07 | Service management method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110631388.5A CN113220540B (en) | 2021-06-07 | 2021-06-07 | Service management method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113220540A true CN113220540A (en) | 2021-08-06 |
| CN113220540B CN113220540B (en) | 2023-04-25 |
Family
ID=77083072
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110631388.5A Active CN113220540B (en) | 2021-06-07 | 2021-06-07 | Service management method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113220540B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113704016A (en) * | 2021-08-26 | 2021-11-26 | 北京百度网讯科技有限公司 | Cloud function component diagnosis method, device, equipment, storage medium and program product |
| CN114841710A (en) * | 2022-06-30 | 2022-08-02 | 深圳华锐分布式技术股份有限公司 | Method, device, equipment and medium for removing order when transaction system fails |
| CN115086262A (en) * | 2022-06-20 | 2022-09-20 | 深圳证券通信有限公司 | Heterogeneous instant messaging method and related device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104375928A (en) * | 2013-08-12 | 2015-02-25 | 鸿富锦精密工业（深圳）有限公司 | Abnormal log management method and system |
| US20160041863A1 (en) * | 2014-08-07 | 2016-02-11 | Fujitsu Limited | System and abnormal condition detection method |
| CN109783325A (en) * | 2018-12-14 | 2019-05-21 | 平安证券股份有限公司 | Business monitoring method, device, equipment and storage medium |
| CN110223173A (en) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Trade link abnormality eliminating method and relevant device |
| CN110245154A (en) * | 2019-05-20 | 2019-09-17 | 平安科技（深圳）有限公司 | Multichannel links abnormality eliminating method and relevant device |
| CN112486640A (en) * | 2020-11-18 | 2021-03-12 | 中信银行股份有限公司 | Service processing method and device, electronic equipment and computer readable storage medium |
| CN112711520A (en) * | 2020-12-30 | 2021-04-27 | 平安科技（深圳）有限公司 | Method, device and equipment for processing abnormal log information and storage medium |
-
2021
- 2021-06-07 CN CN202110631388.5A patent/CN113220540B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104375928A (en) * | 2013-08-12 | 2015-02-25 | 鸿富锦精密工业（深圳）有限公司 | Abnormal log management method and system |
| US20160041863A1 (en) * | 2014-08-07 | 2016-02-11 | Fujitsu Limited | System and abnormal condition detection method |
| CN109783325A (en) * | 2018-12-14 | 2019-05-21 | 平安证券股份有限公司 | Business monitoring method, device, equipment and storage medium |
| CN110223173A (en) * | 2019-05-20 | 2019-09-10 | 深圳壹账通智能科技有限公司 | Trade link abnormality eliminating method and relevant device |
| CN110245154A (en) * | 2019-05-20 | 2019-09-17 | 平安科技（深圳）有限公司 | Multichannel links abnormality eliminating method and relevant device |
| CN112486640A (en) * | 2020-11-18 | 2021-03-12 | 中信银行股份有限公司 | Service processing method and device, electronic equipment and computer readable storage medium |
| CN112711520A (en) * | 2020-12-30 | 2021-04-27 | 平安科技（深圳）有限公司 | Method, device and equipment for processing abnormal log information and storage medium |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113704016A (en) * | 2021-08-26 | 2021-11-26 | 北京百度网讯科技有限公司 | Cloud function component diagnosis method, device, equipment, storage medium and program product |
| CN113704016B (en) * | 2021-08-26 | 2023-07-28 | 北京百度网讯科技有限公司 | Cloud function component diagnosis method, device, equipment and storage medium |
| CN115086262A (en) * | 2022-06-20 | 2022-09-20 | 深圳证券通信有限公司 | Heterogeneous instant messaging method and related device |
| CN115086262B (en) * | 2022-06-20 | 2023-09-26 | 深圳证券通信有限公司 | Heterogeneous instant messaging method and related device |
| CN114841710A (en) * | 2022-06-30 | 2022-08-02 | 深圳华锐分布式技术股份有限公司 | Method, device, equipment and medium for removing order when transaction system fails |
| CN114841710B (en) * | 2022-06-30 | 2022-10-04 | 深圳华锐分布式技术股份有限公司 | Method, device, equipment and medium for removing order when transaction system fails |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113220540B (en) | 2023-04-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11269718B1 (en) | Root cause detection and corrective action diagnosis system | |
| CN113220540B (en) | Service management method, device, computer equipment and storage medium | |
| US20190378073A1 (en) | Business-Aware Intelligent Incident and Change Management | |
| US9049105B1 (en) | Systems and methods for tracking and managing event records associated with network incidents | |
| CN115190035B (en) | System, method, apparatus, and medium for providing mobile device support services | |
| CN102571403B (en) | The implementation method of general data quality control adapter and device | |
| CN104834602B (en) | A kind of program dissemination method, device and program delivery system | |
| CN111193609B (en) | Application abnormity feedback method and device and application abnormity monitoring system | |
| JP2002108728A (en) | Method for inserting fault information and provider facility | |
| US9779377B2 (en) | Customization of event management and incident management policies | |
| CN110222535B (en) | Processing device, method and storage medium for block chain configuration file | |
| CN105556499A (en) | Intelligent auto-scaling | |
| CN112115026A (en) | Server cluster monitoring method and device, electronic equipment and readable storage medium | |
| CN112737800A (en) | Service node fault positioning method, call chain generation method and server | |
| CN111897697B (en) | Server hardware fault repairing method and device | |
| CN115509858A (en) | Business system monitoring method and device, storage medium and computer equipment | |
| CN110291505A (en) | Reduce the recovery time of application | |
| US20100064290A1 (en) | Computer-readable recording medium storing a control program, information processing system, and information processing method | |
| CN113326052A (en) | Method and device for upgrading service component, computer equipment and storage medium | |
| CN110968456A (en) | Method and device for processing fault disk in distributed storage system | |
| CN110955647A (en) | Database assistance method, database assistance device, computer equipment and storage medium | |
| CN107783852B (en) | Dump file generation method and terminal | |
| WO2019100655A1 (en) | Method and apparatus for constructing invoice requisition anomalies, computer device and storage medium | |
| CN115529250B (en) | Flow playback method and device, electronic equipment and storage medium | |
| CN116719654B (en) | Evaluation method and device of software service, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 2301, building 5, Shenzhen new generation industrial park, 136 Zhongkang Road, Meidu community, Meilin street, Futian District, Shenzhen City, Guangdong Province Applicant after: Shenzhen Huarui Distributed Technology Co.,Ltd. Address before: Room 2301, building 5, Shenzhen new generation industrial park, 136 Zhongkang Road, Meidu community, Meilin street, Futian District, Shenzhen City, Guangdong Province Applicant before: SHENZHEN ARCHFORCE FINANCIAL TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |