CN108733698B - Log message processing method and background service system - Google Patents
Log message processing method and background service system Download PDFInfo
- Publication number
- CN108733698B CN108733698B CN201710257765.7A CN201710257765A CN108733698B CN 108733698 B CN108733698 B CN 108733698B CN 201710257765 A CN201710257765 A CN 201710257765A CN 108733698 B CN108733698 B CN 108733698B
- Authority
- CN
- China
- Prior art keywords
- service node
- message
- rpc
- rpc message
- log
- 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.)
- Active
Links
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/323—Visualisation of programs or trace data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3495—Performance evaluation by tracing or monitoring for systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- 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
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Data Mining & Analysis (AREA)
- Computer And Data Communications (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a log message processing method and a background service system, which can improve the positioning efficiency of problematic service nodes. The method of the embodiment of the invention comprises the following steps: the background service system receives a first remote procedure call protocol (RPC) message sent by a remote terminal; if the first RPC message meets a preset condition, the background service system sets a target identifier in the first RPC message according to the first RPC message to obtain a second RPC message, wherein the target identifier is used for marking the time sequence of each service node when the second RPC message is transmitted to each service node of the background service system; for each service node, when the second RPC message is transmitted to the service node, the background service system generates a log message with a fixed format according to the second RPC message and the acquired current calling information of the second RPC message; the background service system creates a directed acyclic graph having the timing sequence from the log message.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method for processing a log message and a background service system.
Background
Remote procedure call protocol (Remote Procedure Call, RPC), refers to a protocol that requests services from a remote computer program over a network without knowledge of underlying network technology. For example, two servers a and B, one application deployed on server a, want to call functions or methods provided by the application on server B, and because they are not in one memory space, they cannot be directly called, and it is necessary to express the semantics of the call and communicate the data of the call through the network.
The prior proposal provides a log message processing method according to the RPC protocol, in particular: after setting a dyeing mark on an RPC message meeting the condition by an initial service node of a background service system accessed by a remote terminal, transmitting the RPC message with the dyeing mark to a downstream service node, further reporting log messages without fixed formats to a log server in the background service system by each service node through which the RPC message passes, constructing a directed acyclic graph (directed acycline praph, DAG) according to the log messages by the log server, and storing the log messages in a disk file in a concentrated manner.
However, since the time of each service node is not synchronous, determining the time sequence of the RPC message at each service node depending on the time of each service node is unreliable, which results in that the service logic flow of the RPC message cannot be accurately displayed, so that the time sequence relationship of the DAG graph constructed in the existing scheme is inaccurate, and the service node with problem cannot be effectively located through the DAG graph.
Disclosure of Invention
The embodiment of the invention provides a log message processing method and a background service system, which can improve the positioning efficiency of problematic service nodes. .
In view of this, a first aspect of the present invention provides a method for processing a log message, which may include:
the background service system receives a first remote procedure call protocol (RPC) message sent by a remote terminal;
if the first RPC message meets a preset condition, the background service system sets a target identifier in the first RPC message according to the first RPC message to obtain a second RPC message, wherein the target identifier is used for marking the time sequence of each service node when the second RPC message is transmitted to each service node of the background service system;
for each service node, when the second RPC message is transmitted to the service node, the background service system generates a log message with a fixed format according to the second RPC message and the acquired current calling information of the second RPC message;
the background service system creates a directed acyclic graph having the timing sequence from the log message.
A second aspect of an embodiment of the present invention provides a background service system, which may include:
The receiving module is used for receiving a first remote procedure call protocol (RPC) message sent by the remote terminal;
the setting module is used for setting a target identifier in the first RPC message according to the first RPC message if the first RPC message meets preset conditions to obtain a second RPC message, wherein the target identifier is used for marking the time sequence of each service node when the second RPC message is transmitted to each service node of the background service system;
the generation module is used for generating a log message in a fixed format according to the second RPC message and the acquired current calling information of the second RPC message when the second RPC message is transmitted to the service node for each service node;
and the creation module is used for creating the directed acyclic graph with the time sequence according to the log message.
A third aspect of an embodiment of the present invention provides a background service system, which may include: a receiver, a processor, and a memory;
the receiver is used for receiving a first remote procedure call protocol (RPC) message sent by the remote terminal;
the processor is configured to set a target identifier in the first RPC message according to the first RPC message if the first RPC message meets a preset condition, so as to obtain a second RPC message, where the target identifier is used to mark a time sequence of each service node when the second RPC message is transmitted to each service node of the background service system; for each service node, when the second RPC message is transmitted to the service node, generating a log message with a fixed format according to the second RPC message and the acquired current calling information of the second RPC message; creating a directed acyclic graph with the timing from the log message.
The memory is used for storing codes required by the processor to execute corresponding operations.
A fourth aspect of the embodiments of the present invention provides a computer storage medium having stored thereon a computer program, characterized in that the program when executed by a processor performs the steps of the method according to the first aspect of the embodiments of the present invention.
From the above technical solutions, the embodiment of the present invention has the following advantages: because the target identifier in the second RPC message can be used for marking the time sequence of each service node when the second RPC message is transmitted to each service node of the background service system, after the log message is generated on the second RPC message and the corresponding call information, a directed acyclic graph with the time sequence can be constructed through the log message, so that the positioning efficiency of the service node with the problem can be improved under the condition that the time sequence relation of the directed acyclic graph is accurate.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of an operation principle of RPC call according to an embodiment of the present invention;
fig. 2 is a structural diagram of a background service system according to an embodiment of the present invention;
fig. 3 is a flow chart of a log message processing method according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an embodiment of a method for processing a log message according to the present invention;
FIG. 5-a is a directed acyclic graph of a normal call of a service node according to an embodiment of the present invention;
FIG. 5-b is a directed acyclic graph of an abnormal call of a service node according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating another embodiment of a method for processing a log message according to an embodiment of the present invention;
FIG. 7 is a diagram of a background service system according to an embodiment of the present invention;
FIG. 8 is a diagram of another embodiment of a background service system according to an embodiment of the present invention;
fig. 9 is a schematic diagram of another embodiment of a background service system according to an embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a log message processing method and a background service system, which can improve the positioning efficiency of problematic service nodes. .
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented, for example, in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For ease of understanding, the terms that may be involved in the embodiments of the present invention will be first explained:
dyeing: a conditional RPC message is given a special tag that is passed between the serving nodes through which the RPC message passes, thereby being distinguished from other normal messages.
Call chain: the layer-by-layer call relationship between service nodes, with only one node per layer.
DAG: and (3) a directed acyclic graph, wherein each layer has 1 to a plurality of nodes to form a tree call relationship between service nodes.
Globally unique identification (global unique identifier, GUID): globally unique user Identification (ID).
Further, the working principle of RPC call in the embodiment of the present invention is described below, referring to fig. 1, fig. 1 is a schematic diagram of the working principle of RPC call provided in the embodiment of the present invention, as shown in fig. 1, including the following steps:
step (1): invoking a client handle; executing the transmission parameters;
step (2): invoking a local kernel to send a message;
step (3): the message is transmitted to a remote kernel;
step (4): the server handle obtains the message and the parameters;
step (5): requesting execution of a remote procedure from a function in a server;
Step (6): after execution, returning the result to the server handle;
step (7): the server handle returns a result and calls a remote kernel;
step (8): transmitting the result back to the local kernel;
step (9): the client handle receives a result sent by a local kernel;
step (10): the function in the client receives the result returned by the client handle.
The working principle of RPC call in the embodiment of the present invention is introduced above, and the background service system in the embodiment of the present invention is introduced below, as shown in fig. 2, fig. 2 is a structure diagram of a background service system provided in the embodiment of the present invention, where the background service system may include an access service node, a downstream service node of the access service node, and a log service node, and it should be noted that the number of the downstream service nodes may be one or at least two, which is not limited herein. The background service system may further comprise a database for storing log data.
The following describes the flow of the log message processing method in the embodiment of the present invention by taking the background service system shown in fig. 2 as an example, specifically, referring to fig. 3, fig. 3 is a schematic flow diagram of the log message processing method provided in the embodiment of the present invention.
In fig. 3, the log message covers the whole process flow of the background service system, and from the initiation of a request by a remote terminal, a dyeing RPC message is transferred between service nodes until the processing of the current RPC message request is terminated, and the steps are as follows:
step 1: the access service node dyes the RPC message to obtain a dyed RPC message, initiates a request to the service A through a calling interface, generates a log message in a fixed format according to the dyed RPC message and the information of the calling interface, and reports the log message to the log service node.
Step 2: service node A initiates a request to service node B, records the log message and reports to the log service node.
Step 3: the service node B receives the request of the service node A, records the log information and reports the log information to the log service node, and returns the request result to the service node A.
Step 4: the service node A records the request result returned by the service node B, then initiates a request to the service node C, records the log information and reports the log information to the log service node.
Step 5: the service node C receives the request of the service node A, records the log information and reports the log information to the log service node, and returns the request result to the service node A.
Step 6: the service node A records the request result returned by the service node C, records the log information and reports the log information to the log service node, and the database stores the log information.
When the RPC message request processing is terminated, the log service node collects complete call information, and at the moment, the log service node performs DAG analysis on the formatted log message to construct a visual tree-shaped call relation diagram, and in the visual tree-shaped call relation diagram, the service node with the problem can be quickly positioned.
Referring to fig. 4, an embodiment of a method for processing a log message according to an embodiment of the present invention includes:
101. the background service system receives a first remote procedure call protocol (RPC) message sent by a remote terminal;
in this embodiment, when a user needs to invoke an application on a service node in a remote background service system through a remote terminal, the user may send a first RPC message to the background service system through the remote terminal.
In practical application, the background service system may receive RPC messages sent by at least two remote terminals at the same time, which is not limited herein.
In some possible embodiments, an access service node may be included in the background service system, the access service node configured to receive the first RPC message. Thus, the receiving, by the background service system, the first remote procedure call protocol RPC message sent by the remote terminal may be: the background service system receives a first remote procedure call protocol (RPC) message sent by a remote terminal through an access service node.
It should be noted that, the access service node is a root node of a tree structure of service nodes, and the first service node to which all the requests of the remote terminal are sent is the access service node.
102. If the first RPC message meets the preset condition, the background service system sets a target identifier in the first RPC message according to the first RPC message to obtain a second RPC message, wherein the target identifier is used for marking the time sequence of each service node when the second RPC message is transmitted to each service node in the background service system;
in this embodiment, after receiving the first RPC message, the background service system needs to determine whether the first RPC message meets a preset condition, and if the first RPC message meets the preset condition, the background service system sets a target identifier in the first RPC message according to the first RPC message to obtain a second RPC message, where the target identifier is used to mark a time sequence of each service node when the second RPC message is transmitted to each service node of the background service system.
In some possible embodiments, the following determination method is given for whether the first RPC message meets the preset condition, specifically: the background server judges whether the globally unique identifier in the first RPC message is matched with a preset white list; if the first RPC message is matched with the preset condition, the background service system determines that the first RPC message accords with the preset condition; or the background server judges whether the international mobile equipment identification in the first RPC message is matched with a preset white list; if so, the background service system determines that the first RPC message meets the preset condition.
It may be appreciated that the background server may determine through the globally unique identifier or the international mobile equipment identifier in the first RPC message, and if the globally unique identifier or the international mobile equipment identifier hits the white list, determine that the preset condition is met.
It should be noted that, the background server may also determine whether the first RPC message meets the preset condition in other manners, which is not limited herein.
Also, in some possible embodiments, the setting, by the background service system, the target identifier in the first RPC message according to the first RPC message may be: an access service node in a background service system sets a target identifier in a first RPC message according to the first RPC message, wherein the target identifier comprises at least one field as follows: the remote terminal requests serial number, the first RPC message name, the calling chain layer of the target mark, the names of all service nodes and the printing time of the log message.
It can be seen that the destination identifier may be composed of various fields, and in practical applications, the composition field of the destination identifier may be referred to in table 1, and as shown in table 1 below, the composition field may include requestId, method, seq, serverName, serverSeq.
103. For each service node, when the second RPC message is transmitted to the service node, the background service system generates a log message with a fixed format according to the second RPC message and the acquired current calling information of the second RPC message;
In this embodiment, when the second RPC message is transmitted to a certain service node, the background service system determines the service node to which the second RPC message is to be transmitted next, then generates call information of the second RPC message, and finally the background service system may generate a log message in a fixed format according to the second RPC message and the call information of the second RPC message.
It should be noted that the log message may carry the target identifier.
Furthermore, after generating the log message in the fixed format, the background service system may store the log message through a database, thereby, in some possible embodiments, further including: the background service system stores a log message in a format of the log message, wherein the log message comprises a fixed field and a variable parameter field.
Therefore, the log information is stored according to the format of the log information, so that the stored log information is not required to be manually screened for the second time, an effective automatic filtering analysis method is provided, and the technical scheme of the application is perfected.
Optionally, in some possible embodiments, the generating, by the background service system, the log message in the fixed format according to the second RPC message and the obtained current call information of the second RPC message may be: the background service system generates a log message in a fixed format according to the second RPC message, the acquired current calling information of the second RPC message and the acquired current moment.
It should be noted that the background service system may also generate the log message in other manners, which is not limited herein.
In addition, the log message may be composed of fixed fields and variable parameter fields, and in practical applications, the composition fields of the log message may be referred to in table 2, as shown in table 2 below, and the composition fields may include: logname, guid, ime, log _type, cost_ time, desc, ret _code, k1, v1|k2, v2| … |kn, vn.
| Field name | Meaning of field |
| logname | Flow name |
| guid | Guid of remote terminal |
| imei | Imei of remote terminal |
| log_type | Log message type |
| cost_time | Time consuming |
| Desc | Description of the flow |
| ret_code | Return code |
| k1，v1∣k2，v2∣…∣kn，vn | Self-resolved kv list for carrying key result information |
104. The background service system creates a directed acyclic graph with timing from the log message.
In this embodiment, after the background service system generates the log message, the background service system collects the complete call information, and performs DAG analysis on the log message in a fixed format through an algorithm at this time, so that a directed acyclic graph with a time sequence, that is, a visualized tree-shaped call relationship graph can be constructed.
Because the reported log information is input by the algorithm, a plurality of protocol processing processes are generated after the printing time of the log information and the name of the service node are filtered, all record sets belonging to the same protocol processing flow can be screened according to < request, method >, then the elements in the sets are subjected to the algorithm to obtain a visual tree-shaped call relation diagram, and the visual tree-shaped call relation diagram is used for rapidly diagnosing the problem and can be also used for monitoring and analyzing. An alternative algorithm is as follows:
The first step: taking out the element with the minimum seq in the set as a first node;
and a second step of: the tree diagram construction process taking a certain node as a root node, and inputting the tree diagram as a server_name, comprises the following steps of;
1) Taking out all log records of serverName=serverName from the collection, and constructing a visualization node according to the ascending arrangement of serverSeq of each log record;
2) Taking out all the duplicate removal serverNames of the caller=server_name from the collection, and returning if the result is null; otherwise, recursively executing step 1) on each serverName, and connecting the node to the teller node.
The directed acyclic graph generated by the algorithm can be seen in fig. 5-a and fig. 5-b, wherein fig. 5-a is the directed acyclic graph for normal call of service nodes provided by the embodiment of the invention, all the service nodes are in a normal call state, and specific log information can be seen by clicking the service nodes. Fig. 5-b is a directed acyclic graph of abnormal call of a service node, where two service nodes in the middle are in an abnormal call state, and the abnormal service node can be quickly located by clicking.
Alternatively, in some possible embodiments, the creating, by the background service system, a directed acyclic graph with a timing according to a log message may be:
The background service system determines the orderly calling relation of each service node according to the log information;
the background service system creates a directed acyclic graph with a time sequence according to the ordered calling relationship.
In this embodiment, since the target identifier in the second RPC message may be used to mark the timing sequence of each service node when the second RPC message is transmitted to each service node of the background service system, after the log message is generated on the second RPC message and the corresponding call information, the directed acyclic graph with the timing sequence can be constructed through the log message, so that the positioning efficiency of the service node with the problem can be improved under the condition that the timing sequence relationship of the directed acyclic graph is accurate.
Referring to fig. 6, another embodiment of a method for processing a log message according to an embodiment of the present invention includes:
201. the service node receives a first RPC message;
in this embodiment, the service node is any service node in the background service system, and the first RPC message received by the service node may be sent by the remote terminal to the service node, or may be sent by an upstream service node of the service node to the service node.
It will be appreciated that the serving node is an access serving node if the first RPC message is sent by the terminal device to the serving node, and that the serving node is not an access serving node if the first RPC message is sent by a serving node upstream of the serving node to the serving node. The background service system needs to determine whether the service node is an access service node.
202. The background service system judges whether the service node is an access service node, if so, the step 203 is executed, and if not, the step 204 is executed;
in this embodiment, since the service node may or may not be an access service node, the background service system needs to determine whether the service node is an access service node, if so, step 203 is executed, and if not, step 204 is executed.
203. The service node judges whether the first RPC message accords with a preset condition, if so, the step 205 is executed, and if not, the step 201 is executed in a return mode;
in this embodiment, after the background service system determines that the service node is an access service node, the service node determines whether the first RPC message meets a preset condition, that is, the service node determines whether the first RPC message meets a dyeing condition, if yes, step 205 is executed, and if not, step 201 is executed again.
204. The service node determines whether the first RPC message is dyed, if so, then step 206 is executed, and if not, then step 201 is executed back.
In this embodiment, since the service node is not an access service node, the service node needs to determine whether the first RPC message is dyed, if yes, the dyed first RPC message is the second RPC message, step 206 is executed, and if no, step 201 is executed again.
205. The service node dyes the first RPC message to obtain a second RPC message, and then step 206 is executed;
in this embodiment, the service node may set a coloring flag in the first RPC message, thereby obtaining the second RPC message.
206. The service node generates a log message in a fixed format according to the second RPC message and the acquired current calling information of the second RPC message;
in this embodiment, after the service node dyes the first RPC message to obtain the second RPC message, the service node may generate the log message in a fixed format according to the second RPC message and the obtained current call information of the second RPC message.
207. The serving node sends a second RPC message to the downstream serving node.
In this embodiment, after the service node sends the second RPC message to the downstream service node, the service node may report the log message to the log service node.
In this embodiment, the second RPC message carries the dyeing information, so that the dyeing information between the service nodes establishes an orderly association, and after the log message is generated on the second RPC message and the corresponding call information, a directed acyclic graph with a time sequence can be constructed through the log message, so that the positioning efficiency of the service node with a problem can be improved under the condition that the time sequence relationship of the directed acyclic graph is accurate.
Referring to fig. 7, an embodiment of a background service system in an embodiment of the present invention includes:
a receiving module 301, configured to receive a first remote procedure call protocol RPC message sent by a remote terminal;
a setting module 302, configured to set a target identifier in the first RPC message according to the first RPC message if the first RPC message meets a preset condition, so as to obtain a second RPC message, where the target identifier is used to mark a time sequence of each service node when the second RPC message is transmitted to each service node of the background service system;
a generating module 303, configured to generate, for each service node, when the second RPC message is transmitted to the service node, a log message in a fixed format according to the second RPC message and the acquired current call information of the second RPC message;
a creation module 304 is configured to create a directed acyclic graph with timing from the log message.
In this embodiment, since the target identifier in the second RPC message may be used to mark the timing sequence of each service node when the second RPC message is transmitted to each service node of the background service system, after the log message is generated on the second RPC message and the corresponding call information, the directed acyclic graph with the timing sequence can be constructed through the log message, so that the positioning efficiency of the service node with the problem can be improved under the condition that the timing sequence relationship of the directed acyclic graph is accurate.
Optionally, in some possible embodiments, the setting module 302 is specifically configured to set, by an access service node in the background service system, a target identifier in the first RPC message, where the target identifier includes at least one of the following fields: the remote terminal requests serial number, the first RPC message name, the calling chain layer of the target mark, the names of all service nodes and the printing time of the log message.
Optionally, referring to fig. 8, in some possible embodiments, the system further comprises:
a judging module 401, configured to judge whether the globally unique identifier in the first RPC message matches with a preset whitelist;
a determining module 402, configured to determine that the first RPC message meets a preset condition if the first RPC message matches; or alternatively, the first and second heat exchangers may be,
the judging module 401 is further configured to judge whether the international mobile equipment identifier in the first RPC message is matched with a preset white list;
the determining module 402 is further configured to determine that the first RPC message meets a preset condition if the first RPC message matches.
Further, the system further comprises:
a storage module 403, configured to store a log message according to a format of the log message, where the log message includes a fixed field and a variable parameter field.
Therefore, the log information is stored according to the format of the log information, so that the stored log information is not required to be manually screened for the second time, an effective automatic filtering analysis method is provided, and the technical scheme of the application is perfected.
Optionally, in some possible embodiments, the creating module 304 is specifically configured to determine an orderly calling relationship of each service node according to the log message; a directed acyclic graph having a timing is created from the ordered call relationships.
The background service system in the embodiment of the present invention is described above from the point of view of the modularized functional entity, and the background service system in the embodiment of the present invention is described below from the point of view of hardware processing, referring to fig. 9, where the background service system in the embodiment of the present invention includes: a receiver 501, a processor 502 and a memory 503.
The background service system according to embodiments of the present invention may have more or less components than those shown in fig. 9, may combine two or more components, or may have different component configurations or devices, each of which may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.
The receiver 501 is configured to perform the following operations:
receiving a first remote procedure call protocol (RPC) message sent by a remote terminal;
the processor 502 is configured to perform the following operations:
if the first RPC message meets the preset condition, setting a target identifier in the first RPC message according to the first RPC message to obtain a second RPC message, wherein the target identifier is used for marking the time sequence of each service node when the second RPC message is transmitted to each service node of a background service system; for each service node, when the second RPC message is transmitted to the service node, generating a log message with a fixed format according to the second RPC message and the acquired current calling information of the second RPC message; a directed acyclic graph is created from the log message having a timing.
The memory 503 is used to store code required by the processor 502 to perform the corresponding operations.
In this embodiment, since the target identifier in the second RPC message may be used to mark the timing sequence of each service node when the second RPC message is transmitted to each service node of the background service system, after the log message is generated on the second RPC message and the corresponding call information, the directed acyclic graph with the timing sequence can be constructed through the log message, so that the positioning efficiency of the service node with the problem can be improved under the condition that the timing sequence relationship of the directed acyclic graph is accurate.
Optionally, the processor 502 is further configured to perform the following operations:
setting a target identifier in a first RPC message through an access service node in a background service system, wherein the target identifier comprises at least one field as follows: the remote terminal requests serial number, the first RPC message name, the calling chain layer of the target mark, the names of all service nodes and the printing time of the log message.
Optionally, the processor 502 is further configured to perform the following operations:
judging whether the globally unique identifier in the first RPC message is matched with a preset white list or not; if the first RPC message is matched with the first RPC message, determining that the first RPC message meets a preset condition; or alternatively, the first and second heat exchangers may be,
Judging whether the international mobile equipment identification in the first RPC message is matched with a preset white list or not; if so, determining that the first RPC message meets the preset condition.
Optionally, the memory 503 is further configured to store the log message in a format of the log message, where the log message includes a fixed field and a variable parameter field.
Therefore, the log information is stored according to the format of the log information, so that the stored log information is not required to be manually screened for the second time, an effective automatic filtering analysis method is provided, and the technical scheme of the application is perfected.
Optionally, the processor 502 is further configured to perform the following operations:
determining an ordered calling relation of each service node according to the log message; a directed acyclic graph having a timing is created from the ordered call relationships.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may 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 instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (4)
1. A method for processing a log message, comprising:
for any service node in a background service system, the service node receives a first remote procedure call protocol (RPC) message; the background service system can simultaneously receive RPC messages sent by at least two remote terminals; the background service system comprises an access service node, wherein the access service node is a root node of a tree-shaped architecture of the service node, and all requests of a remote terminal are firstly sent to the access service node;
if the first RPC message received by the service node is sent to the service node by the remote terminal, determining the service node as an access service node;
If the service node is an access service node, the background service system judges whether the first RPC message meets a preset condition, and specifically includes: the background server judges whether the global unique identifier in the first RPC message is matched with a preset white list, if so, the background service system determines that the first RPC message meets preset conditions; or the background server judges whether the international mobile equipment identification in the first RPC message is matched with the preset white list, if so, the background service system determines that the first RPC message meets the preset condition;
if the first RPC message meets a preset condition, setting a target identifier in the first RPC message by an access service node in the background service system according to the first RPC message to obtain a second RPC message, wherein the target identifier is used for marking the time sequence of each service node when the second RPC message is transmitted to each service node of the background service system;
if the first RPC message does not meet the preset condition, returning to execute any service node in the background service system, wherein the service node receives a first remote procedure call protocol (RPC) message;
If the first RPC message received by the service node is sent to the service node by an upstream service node of the service node, but not by the remote terminal, determining that the service node is not an access service node;
if the service node is not an access service node, judging whether the first RPC message is provided with a target identifier or not through the service node;
if the first RPC message has set a target identifier, determining the first RPC message as the second RPC message, generating a log message in a fixed format according to the second RPC message, the acquired current calling information of the second RPC message and the acquired current time, and then transmitting the second RPC message to a downstream service node;
if the target identifier is not set in the first RPC message, returning to execute the step of receiving the first remote procedure call protocol RPC message for any service node in the background service system;
for each service node, when the second RPC message is transmitted to the service node, the background service system generates a log message with a fixed format according to the second RPC message, the acquired current call information of the second RPC message and the acquired current moment, and stores the log message according to the fixed format, so that manual secondary screening of the stored log message is not needed; the target identification comprises: the request serial number of the remote terminal, the first RPC message name, the call chain hierarchy of the target identifier, the names of all service nodes and the printing time of the log message; the composition fields of the log message comprise fixed fields and variable parameter fields, and specifically comprise: flow name, guid of remote terminal, IMEI of remote terminal, log message type, time consumption, flow description, return code and self-resolved kv list; the self-resolved kv list is used for carrying key result information;
The background service system filters a plurality of protocol processing flows according to the log message, the printing time of the log message and the names of the service nodes, and screens all record sets belonging to the same protocol processing flow according to the request serial number of the remote terminal and the first RPC message name;
taking out an element with the smallest calling chain hierarchy of the target mark in the record set as a head node;
taking the input target service node name as a root node, taking out all log records of the target service node name from the record set, and arranging in ascending order according to the printing time of the log message in each log record to construct a visualized node;
and taking out the service node names called by the target service node names from the record set, recursively executing all log records taking out the target service node names from the record set by taking each service node name called by the target service node names as a target service node name, and carrying out ascending arrangement according to the printing time of the log message in each log record to construct a visualized node until the service node names called by the target service node names do not exist, thereby obtaining the directed acyclic graph with the time sequence.
2. A background service system, comprising:
the receiving module is used for receiving a first remote procedure call protocol (RPC) message for any service node in the background service system; the background service system can simultaneously receive RPC messages sent by at least two remote terminals; the background service system comprises an access service node, wherein the access service node is a root node of a tree-shaped architecture of the service node, and all requests of a remote terminal are firstly sent to the access service node; if the first RPC message received by the service node is sent to the service node by the remote terminal, determining the service node as an access service node;
the judging module is used for judging whether the first RPC message accords with a preset condition if the service node is an access service node;
the setting module is used for setting a target identifier in the first RPC message according to the first RPC message by an access service node in the background service system if the first RPC message meets preset conditions to obtain a second RPC message, wherein the target identifier is used for marking the time sequence of each service node when the second RPC message is transmitted to each service node of the background service system; if the first RPC message does not meet the preset condition, returning to execute any service node in the background service system, wherein the service node receives a first remote procedure call protocol (RPC) message;
The background service system is further configured to determine that the service node is not an access service node if the first RPC message received by the service node is sent by an upstream service node of the service node to the service node, but not by the remote terminal to the service node; if the service node is not an access service node, judging whether the first RPC message is provided with a target identifier or not through the service node; if the first RPC message has set a target identifier, determining the first RPC message as the second RPC message, generating a log message in a fixed format according to the second RPC message, the acquired current calling information of the second RPC message and the acquired current time, and then transmitting the second RPC message to a downstream service node; if the target identifier is not set in the first RPC message, returning to execute the step of receiving the first remote procedure call protocol RPC message for any service node in the background service system;
the generation module is used for generating a log message with a fixed format according to the second RPC message, the acquired current calling information of the second RPC message and the acquired current moment when the second RPC message is transmitted to the service node, and storing the log message according to the fixed format, so that manual secondary screening of the stored log message is not needed; the target identification comprises: the request serial number of the remote terminal, the first RPC message name, the call chain hierarchy of the target identifier, the names of all service nodes and the printing time of the log message;
The creation module is used for filtering according to the log message, the printing time of the log message and the names of the service nodes, and then a plurality of protocol processing flows are provided, and all record sets belonging to the same protocol processing flow are screened according to the request serial number of the remote terminal and the first RPC message name; taking out an element with the smallest calling chain hierarchy of the target mark in the record set as a head node; taking the input target service node name as a root node, taking out all log records of the target service node name from the record set, and arranging in ascending order according to the printing time of the log message in each log record to construct a visualized node; taking out the service node names called by the target service node names from the record set, recursively executing all log records taking out the target service node names from the record set by taking each service node name called by the target service node names as a target service node name, and carrying out ascending arrangement according to the printing time of the log message in each log record to construct a visualized node until the service node names called by the target service node names do not exist, so as to obtain a directed acyclic graph with the time sequence;
The system further comprises: a determining module;
the judging module is used for judging whether the globally unique identifier in the first RPC message is matched with a preset white list or not;
the determining module is used for determining that the first RPC message accords with a preset condition if the first RPC message is matched with the first RPC message; or alternatively, the first and second heat exchangers may be,
the judging module is further configured to judge whether an international mobile equipment identifier in the first RPC message is matched with the preset whitelist;
the determining module is further configured to determine that the first RPC message meets a preset condition if the first RPC message matches;
the generation module is specifically configured to store the log message according to a format of the log message, where the log message includes a fixed field and a variable parameter field, and specifically includes: flow name, guid of remote terminal, IMEI of remote terminal, log message type, time consumption, flow description, return code and self-resolved kv list; the self-resolved kv list is used for carrying key result information.
3. A background service system, comprising: a receiver, a processor, and a memory;
the receiver is configured to, for any service node in the background service system, receive a first remote procedure call protocol RPC message; the background service system can simultaneously receive RPC messages sent by at least two remote terminals; the background service system comprises an access service node, wherein the access service node is a root node of a tree-shaped architecture of the service node, and all requests of a remote terminal are firstly sent to the access service node; if the first RPC message received by the service node is sent to the service node by the remote terminal, determining the service node as an access service node;
The processor is configured to determine whether the first RPC message meets a preset condition if the service node is an access service node, and specifically includes: the background server judges whether the global unique identifier in the first RPC message is matched with a preset white list, if so, the background service system determines that the first RPC message meets preset conditions; or the background server judges whether the international mobile equipment identification in the first RPC message is matched with the preset white list, if so, the background service system determines that the first RPC message meets the preset condition; if the first RPC message meets a preset condition, setting a target identifier in the first RPC message by an access service node in the background service system according to the first RPC message to obtain a second RPC message, wherein the target identifier is used for marking the time sequence of each service node when the second RPC message is transmitted to each service node of the background service system; if the first RPC message does not meet the preset condition, returning to execute any service node in the background service system, wherein the service node receives a first remote procedure call protocol (RPC) message; if the first RPC message received by the service node is sent to the service node by an upstream service node of the service node, but not by the remote terminal, determining that the service node is not an access service node; if the service node is not an access service node, judging whether the first RPC message is provided with a target identifier or not through the service node; if the first RPC message has set a target identifier, determining the first RPC message as the second RPC message, generating a log message in a fixed format according to the second RPC message, the acquired current calling information of the second RPC message and the acquired current time, and then transmitting the second RPC message to a downstream service node; if the target identifier is not set in the first RPC message, returning to execute the step of receiving the first remote procedure call protocol RPC message for any service node in the background service system; for each service node, when the second RPC message is transmitted to the service node, generating a log message with a fixed format according to the second RPC message, the acquired current calling information of the second RPC message and the acquired current moment, and storing the log message with the fixed format, so that manual secondary screening of the stored log message is not needed; the target identification comprises: the request serial number of the remote terminal, the first RPC message name, the call chain hierarchy of the target identifier, the names of all service nodes and the printing time of the log message; filtering according to the printing time of the log message and the names of the service nodes and then a plurality of protocol processing flows, and screening all record sets belonging to the same protocol processing flow according to the request serial number of the remote terminal and the first RPC message name; taking out an element with the smallest calling chain hierarchy of the target mark in the record set as a head node; taking the input target service node name as a root node, taking out all log records of the target service node name from the record set, and arranging in ascending order according to the printing time of the log message in each log record to construct a visualized node; taking out the service node names called by the target service node names from the record set, recursively executing all log records taking out the target service node names from the record set by taking each service node name called by the target service node names as a target service node name, and carrying out ascending arrangement according to the printing time of the log message in each log record to construct a visualized node until the service node names called by the target service node names do not exist, so as to obtain a directed acyclic graph with the time sequence; the composition fields of the log message comprise fixed fields and variable parameter fields, and specifically comprise: flow name, guid of remote terminal, IMEI of remote terminal, log message type, time consumption, flow description, return code and self-resolved kv list; the self-resolved kv list is used for carrying key result information;
The memory is used for storing codes required by the processor to execute corresponding operations.
4. A computer storage medium having stored thereon a computer program which when executed by a processor performs the steps of the method according to claim 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710257765.7A CN108733698B (en) | 2017-04-19 | 2017-04-19 | Log message processing method and background service system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710257765.7A CN108733698B (en) | 2017-04-19 | 2017-04-19 | Log message processing method and background service system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108733698A CN108733698A (en) | 2018-11-02 |
| CN108733698B true CN108733698B (en) | 2023-08-08 |
Family
ID=63925352
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710257765.7A Active CN108733698B (en) | 2017-04-19 | 2017-04-19 | Log message processing method and background service system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108733698B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111382056B (en) * | 2018-12-29 | 2024-02-02 | 北京字节跳动网络技术有限公司 | Service testing method and device, server and storage medium |
| CN111131296B (en) * | 2019-12-30 | 2022-04-26 | 杭州迪普科技股份有限公司 | Message distribution method and device |
| CN111427684B (en) * | 2020-03-20 | 2023-04-07 | 支付宝(杭州)信息技术有限公司 | Service deployment method, system and device |
| CN112417843B (en) * | 2020-10-20 | 2024-03-08 | 湖南中广汇智信息技术有限公司 | IDcode identification analysis system and implementation method thereof |
| CN112346672B (en) * | 2020-11-06 | 2023-01-03 | 深圳市同行者科技有限公司 | Log dyeing method, device, equipment and storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8555297B1 (en) * | 2008-09-29 | 2013-10-08 | Emc Corporation | Techniques for performing a remote procedure call using remote procedure call configuration information |
| CN103856534A (en) * | 2012-12-05 | 2014-06-11 | 腾讯科技（深圳）有限公司 | Method and system for collecting logs based on peer-to-peer network |
| CN105138615A (en) * | 2015-08-10 | 2015-12-09 | 北京思特奇信息技术股份有限公司 | Method and system for building big data distributed log |
| CN105224445A (en) * | 2015-10-28 | 2016-01-06 | 北京汇商融通信息技术有限公司 | Distributed tracking system |
| CN105260292A (en) * | 2015-10-09 | 2016-01-20 | 中国人民财产保险股份有限公司 | Log recording method, apparatus and system |
| US9270553B1 (en) * | 2014-03-26 | 2016-02-23 | Amazon Technologies, Inc. | Dynamic service debugging in a virtual environment |
| CN105872578A (en) * | 2016-03-30 | 2016-08-17 | 青岛海信电器股份有限公司 | Invoking method and server |
| CN105933163A (en) * | 2016-06-24 | 2016-09-07 | 微梦创科网络科技（中国）有限公司 | Real-time distributed debugging tracking method and system |
| CN106254144A (en) * | 2016-09-06 | 2016-12-21 | 华为技术有限公司 | Fault location platform, Fault Locating Method and device |
| CN106354765A (en) * | 2016-08-19 | 2017-01-25 | 广东亿迅科技有限公司 | Log analysis system and method based on distributed collection |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN106487805A (en) * | 2016-11-15 | 2017-03-08 | 乐视控股（北京）有限公司 | A kind of remote procedure call tracking and device |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004288026A (en) * | 2003-03-24 | 2004-10-14 | Fuji Xerox Co Ltd | Service processing system, method for recognizing processing result of service processing system, and service processing program |
| JP2007058414A (en) * | 2005-08-23 | 2007-03-08 | Hitachi Ltd | Log management program for computer, its log management method, and computer system |
| US8635617B2 (en) * | 2010-09-30 | 2014-01-21 | Microsoft Corporation | Tracking requests that flow between subsystems using transaction identifiers for generating log data |
| SG11201407780PA (en) * | 2012-05-31 | 2014-12-30 | Netsweeper Barbados Inc | Policy service logging using graph structures |
| US9135145B2 (en) * | 2013-01-28 | 2015-09-15 | Rackspace Us, Inc. | Methods and systems of distributed tracing |
| US9495378B2 (en) * | 2013-08-27 | 2016-11-15 | Purdue Research Foundation | Tracing message transmissions between communications network devices |
-
2017
- 2017-04-19 CN CN201710257765.7A patent/CN108733698B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8555297B1 (en) * | 2008-09-29 | 2013-10-08 | Emc Corporation | Techniques for performing a remote procedure call using remote procedure call configuration information |
| CN103856534A (en) * | 2012-12-05 | 2014-06-11 | 腾讯科技（深圳）有限公司 | Method and system for collecting logs based on peer-to-peer network |
| US9270553B1 (en) * | 2014-03-26 | 2016-02-23 | Amazon Technologies, Inc. | Dynamic service debugging in a virtual environment |
| CN105138615A (en) * | 2015-08-10 | 2015-12-09 | 北京思特奇信息技术股份有限公司 | Method and system for building big data distributed log |
| CN105260292A (en) * | 2015-10-09 | 2016-01-20 | 中国人民财产保险股份有限公司 | Log recording method, apparatus and system |
| CN105224445A (en) * | 2015-10-28 | 2016-01-06 | 北京汇商融通信息技术有限公司 | Distributed tracking system |
| CN105872578A (en) * | 2016-03-30 | 2016-08-17 | 青岛海信电器股份有限公司 | Invoking method and server |
| CN105933163A (en) * | 2016-06-24 | 2016-09-07 | 微梦创科网络科技（中国）有限公司 | Real-time distributed debugging tracking method and system |
| CN106354765A (en) * | 2016-08-19 | 2017-01-25 | 广东亿迅科技有限公司 | Log analysis system and method based on distributed collection |
| CN106254144A (en) * | 2016-09-06 | 2016-12-21 | 华为技术有限公司 | Fault location platform, Fault Locating Method and device |
| CN106487596A (en) * | 2016-10-26 | 2017-03-08 | 宜人恒业科技发展（北京）有限公司 | Distributed Services follow the tracks of implementation method |
| CN106487805A (en) * | 2016-11-15 | 2017-03-08 | 乐视控股（北京）有限公司 | A kind of remote procedure call tracking and device |
Non-Patent Citations (1)
| Title |
|---|
| 分布式环境下软件性能追踪工具的设计与实现;李健;《中国优秀硕士学位论文全文数据库 信息科技辑》;20150215;文章第10-12，23-24，37-39页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108733698A (en) | 2018-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108733698B (en) | Log message processing method and background service system | |
| US20220070071A1 (en) | Data handler | |
| US11856426B2 (en) | Network analytics | |
| CN111355802B (en) | Information pushing method and device | |
| WO2016079046A1 (en) | Diagnostic testing in networks | |
| CN104468207B (en) | The method, apparatus and system of terminal management | |
| CN112491719A (en) | Network node selection method, equipment and storage medium | |
| CN106936660B (en) | Data acquisition method and device | |
| EP4097924A1 (en) | Classifying traffic data | |
| CN115104336A (en) | Tracking and publishing data for generating analytics | |
| CN111327466A (en) | Alarm analysis method, system, equipment and medium | |
| CN107171873A (en) | A kind of method and apparatus of Message Processing | |
| US7301910B2 (en) | Methods and systems for automated analysis of signaling link utilization | |
| CN106959903A (en) | Trap instruction Trap processing method and processing device | |
| CN105607983B (en) | Data exception monitoring method and device | |
| CN116974805A (en) | Root cause determination method, apparatus and storage medium | |
| CN103326892B (en) | The operating method and device of web interface | |
| CN109450103A (en) | Condition detection method, device and the intelligent terminal of pressing plate | |
| JP6712560B2 (en) | Information processing device, information processing method, and program | |
| CN106777010B (en) | Log providing method and device and log obtaining method, device and system | |
| CN110442588A (en) | Information synchronous updating method, device, computer equipment and storage medium | |
| CN110196874A (en) | Data subscription method, device and server | |
| WO2022174362A1 (en) | Entities and methods for trained data model selection in 5g mobile networks | |
| CN114679487B (en) | Link processing method, device, storage medium and processor | |
| CN115827678B (en) | Method, device, medium and electronic equipment for acquiring service data |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |