CN113434399B - Service node log processing method and device, storage medium and electronic device - Google Patents
Service node log processing method and device, storage medium and electronic device Download PDFInfo
- Publication number
- CN113434399B CN113434399B CN202110701570.3A CN202110701570A CN113434399B CN 113434399 B CN113434399 B CN 113434399B CN 202110701570 A CN202110701570 A CN 202110701570A CN 113434399 B CN113434399 B CN 113434399B
- Authority
- CN
- China
- Prior art keywords
- target service
- nodes
- service node
- server
- determining
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3636—Software debugging by tracing the execution of the program
-
- 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/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/449—Object-oriented method invocation or resolution
-
- 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
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a processing method and a processing device of a service node log, a storage medium and an electronic device, wherein the processing method comprises the following steps: obtaining a target service node, wherein the target service node is a node which has no calling relation in the interaction process of a client and a server; marking the target service node by adopting a preset point location type to obtain a preset buried point; and determining the log of the target service node according to the preset buried point. By adopting the technical scheme, the technical problem that related information of the node without calling relationship in the service execution process cannot be known in the related technology is solved.
Description
Technical Field
The present invention relates to the technical field of software development services, and in particular, to a method and an apparatus for processing a service node log, a storage medium, and an electronic apparatus.
Background
In the field of software development business of log tracking, a general model is to mark the logs of both interface calling sides according to CS/CR/SS/SR, and identify the condition of interface calling. Fig. 1 is a schematic diagram of a generic model of a service interface in the prior art, and as shown in fig. 1, data transmitted by each service interface (node) has a uTraceId and a uspan id.
In a distributed request link, there are a uTraceId and a uspan id for data to be transmitted in a network, and a call between any two nodes needs to be buried at two points at a calling end and a service end, and fig. 2 is a schematic diagram of a buried point in a process of interaction between a client and the service end in the prior art, as shown in fig. 2:
client end (CS): the client buries the point when initiating the request, and uTraceId, uSpanId is the data needed to be transferred to the lower node.
Server Receiver (SR): the server receives the request, buries the point, acquires uTraceId, uSpanId transmitted by the request, and puts the uTraceId, uSpanId into the processing context.
Server Send (SS): the server side buries the point when sending the request processing result to the client side.
Client Reagent (CR): the client receives the response embedded point of the server.
It can be seen that the prior art covers nodes with upstream and downstream relations, but some service nodes do not have such calling relations, but record steps of service execution, and for such nodes, the original technology is not related, that is, for interfaces without interface interaction, the prior art cannot cover the process of calling interfaces.
Therefore, for the technical scheme in the prior art, the related information of the node without the calling relationship in the service execution process cannot be obtained.
Aiming at the technical problem that the related information of the node without the calling relationship in the service execution process cannot be known in the related technology, no effective solution is proposed yet.
Disclosure of Invention
The embodiment of the invention provides a processing method and device of a service node log, a storage medium and an electronic device, which at least solve the technical problem that related information of a node without a calling relationship in a service executing process cannot be known in the related technology.
According to an embodiment of the present invention, there is provided a method for processing a service node log, including: obtaining a target service node, wherein the target service node is a node which has no calling relation in the interaction process of a client and a server; marking the target service node by adopting a preset point location type to obtain a preset buried point; and determining the log of the target service node according to the preset buried point.
In one exemplary embodiment, obtaining a target service node includes: determining nodes with calling relations in the interaction process of the client and the server, wherein the client and the server are respectively provided with two nodes with calling relations; and determining the target service node according to the two nodes with calling relations of the client and/or according to the two nodes with calling relations of the server.
In an exemplary embodiment, determining the target service node according to two nodes with calling relationships of the client and/or according to two nodes with calling relationships of the server includes: screening out nodes without calling relations from two nodes with calling relations of the client, and determining the nodes without calling relations as the target service nodes; and/or screening out the node without calling relation from the two nodes with calling relation at the server, and determining the node without calling relation as the target service node.
In an exemplary embodiment, when the number of the target service nodes is multiple, identifying the target service nodes by adopting a preset point location type to obtain a preset buried point includes: screening out target service nodes to be identified from a plurality of target service nodes; and identifying the target service node to be identified according to the preset point location type, and obtaining the preset buried points in the target service nodes.
In an exemplary embodiment, determining the log of the target service node according to the preset buried point includes: recording parameter data of the target service node in the service execution process according to the preset buried point; and determining the parameter data as the log of the target service node.
In an exemplary embodiment, the parameter data includes at least one of: the end time of service execution, the error code of service execution, the time spent on service execution, the number of reconnections of service execution.
In an exemplary embodiment, after determining the log of the target service node, the method further includes: and calling the preset buried point corresponding to the target service node, and determining the problem of the target service node in the service execution process.
According to another embodiment of the present invention, there is also provided a processing apparatus for a service node log, including: the system comprises an acquisition module, a service server and a service server, wherein the acquisition module is used for acquiring a target service node, wherein the target service node is a node which does not have a calling relationship in the interaction process of the client and the service server; the identification module is used for identifying the target service node by adopting a preset point location type to obtain a preset buried point; and the determining module is used for determining the log of the target service node according to the preset buried point.
In one exemplary embodiment, the acquisition module includes: the first determining unit is used for determining nodes with calling relations in the interaction process of the client and the server, wherein the client and the server are respectively provided with two nodes with calling relations; and the second determining unit is used for determining the target service node according to the two nodes with calling relations of the client and/or according to the two nodes with calling relations of the server.
In an exemplary embodiment, the second determining unit includes: a first determining subunit, configured to screen a node that does not have a calling relationship from between two nodes that have a calling relationship of the client, and determine the node that does not have a calling relationship as the target service node; and/or a second determining subunit, configured to screen a node that does not have a calling relationship from between two nodes that have a calling relationship of the server, and determine the node that does not have a calling relationship as the target service node.
In an exemplary embodiment, when the number of the target service nodes is a plurality, the identification module includes: the screening unit is used for screening target service nodes to be identified from a plurality of target service nodes; the identification unit is used for identifying the target service node to be identified according to the preset point location type, and obtaining the preset buried points in the target service nodes.
In one exemplary embodiment, the determining module includes: the recording unit is used for recording parameter data of the target service node in the service execution process according to the preset buried point; and the third determining unit is used for determining the parameter data as the log of the target service node.
In an exemplary embodiment, the parameter data includes at least one of: the end time of service execution, the error code of service execution, the time spent on service execution, the number of reconnections of service execution.
In an exemplary embodiment, the apparatus further comprises: and the calling module is used for calling the preset buried point corresponding to the target service node after determining the log of the target service node, and determining the problem of the target service node in the service execution process.
According to yet another aspect of the embodiments of the present invention, there is also provided a computer readable storage medium having a computer program stored therein, wherein the computer program is configured to execute the above-mentioned processing method of service node logs when running.
According to still another aspect of the embodiment of the present invention, there is further provided an electronic device, including a memory, a processor, and a computer program stored on the memory and capable of running on the processor, where the processor executes the above-mentioned processing method of service node logs by using the computer program.
In the embodiment of the invention, a target service node is obtained, wherein the target service node is a node which has no calling relationship in the interaction process of a client and a server; marking the target service node by adopting a preset point location type to obtain a preset buried point; and determining the log of the target service node according to the preset buried point. By adopting the technical scheme, the technical problem that the related information of the node without the calling relationship in the service execution process cannot be known in the related technology is solved, so that the interface or step without interactive behavior is recorded, and the technical effect of acquiring the related information of the node without the calling relationship in the service execution process is realized.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a schematic diagram of a generic model of a business interface in the prior art;
FIG. 2 is a schematic diagram of a buried point in the prior art during a client-server interaction;
fig. 3 is a hardware block diagram of a computer terminal of a processing method of a service node log according to an embodiment of the present invention;
FIG. 4 is a flow chart of a method of processing a service node log according to an embodiment of the invention;
FIG. 5 is a schematic diagram of a method of processing a service node log according to an embodiment of the present invention;
fig. 6 is a block diagram of a processing apparatus for service node log according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures 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 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.
The method embodiments provided by the embodiments of the present application may be performed in a computer terminal, or a similar computing device. Taking the operation on a computer terminal as an example, fig. 3 is a block diagram of a hardware structure of a computer terminal of a processing method of a service node log according to an embodiment of the present invention. As shown in fig. 3, the computer terminal may include one or more (only one is shown in fig. 3) processors 302 (the processor 302 may include, but is not limited to, a microprocessor MCU or a processing device such as a programmable logic device FPGA) and a memory 304 for storing data, and in one exemplary embodiment, may also include a transmission device 306 for communication functions and an input-output device 308. It will be appreciated by those skilled in the art that the configuration shown in fig. 3 is merely illustrative and is not intended to limit the configuration of the computer terminal described above. For example, the computer terminal may also include more or fewer components than shown in FIG. 3, or have a different configuration than the equivalent functions shown in FIG. 3 or more than the functions shown in FIG. 3.
The memory 304 may be used to store computer programs, such as software programs of application software and modules, such as computer programs corresponding to the method for processing service node logs in the embodiment of the present invention, and the processor 302 executes the computer programs stored in the memory 304, thereby performing various functional applications and data processing, that is, implementing the method described above. Memory 304 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 304 may further include memory located remotely from processor 302, which may be connected to the computer terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission means 306 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of a computer terminal. In one example, the transmission device 306 includes a network adapter (Network Interface Controller, simply referred to as NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 306 may be a Radio Frequency (RF) module, which is used to communicate with the internet wirelessly.
In this embodiment, a method for processing a service node log is provided and applied to the computer terminal, and fig. 4 is a flowchart of a method for processing a service node log according to an embodiment of the present invention, as shown in fig. 4, where the flowchart includes the following steps:
step S402, a target service node is obtained, wherein the target service node is a node which does not have a calling relationship in the interaction process of a client and a server;
it should be noted that, a node that does not have a call relationship in the process of interaction between the client and the server may be used as a target service node, where the target service node includes, but is not limited to, an interface or a step that does not have an interaction behavior in the process of interaction between the client and the server.
Step S404, marking the target service node by adopting a preset point location type to obtain a preset buried point;
the preset point type may be a log embedded point customized by the service end or an embedded point other than CS, CR, SR, SS embedded point.
Step S406, determining the log of the target service node according to the preset buried point.
Optionally, the node without calling relation in the interaction process of the client and the server can be embedded by using the preset embedded point, so that the log of the node is obtained.
It should be noted that, the log includes parameter data of the target service node in the service execution process based on the preset embedded point record.
In an optional implementation manner, the client and the server are respectively provided with an asynchronous queue, wherein the asynchronous queue corresponding to the client is used for reporting the client context data in the interaction process of the client and the server, and the asynchronous queue corresponding to the server is used for reporting the server context data in the interaction process of the client and the server.
Through the steps, the target service node is obtained, wherein the target service node is a node which has no calling relation in the interaction process of the client and the server; marking the target service node by adopting a preset point location type to obtain a preset buried point; and determining the log of the target service node according to the preset buried point. By adopting the technical scheme, the technical problem that the related information of the node without the calling relationship in the service execution process cannot be known in the related technology is solved, so that the interface or step without interactive behavior is recorded, and the technical effect of acquiring the related information of the node without the calling relationship in the service execution process is realized.
The step S402 may have various implementation manners, and the embodiment of the present invention mainly provides three implementation manners:
scheme one:
step S10: determining nodes with calling relations in the interaction process of the client and the server, wherein the client and the server are respectively provided with two nodes with calling relations;
step S12: and determining a target service node according to the two nodes with calling relations of the client.
Scheme II:
step S20: determining nodes with calling relations in the interaction process of the client and the server, wherein the client and the server are respectively provided with two nodes with calling relations;
step S22: and determining a target service node according to the two nodes with calling relations of the server.
Scheme III:
step S30: determining nodes with calling relations in the interaction process of the client and the server, wherein the client and the server are respectively provided with two nodes with calling relations;
step S32: and determining the target service node according to the two nodes with calling relations of the client and the two nodes with calling relations of the server.
In other words, firstly, the node with the calling relationship in the interaction process of the client and the server needs to be determined, in general, the client is provided with two nodes with the calling relationship, correspondingly, the server is also correspondingly provided with two nodes with the calling relationship, and secondly, the target service node can be obtained according to the two nodes with the calling relationship of the client and/or the two nodes with the calling relationship of the server. It should be noted that, the target service node may be between two nodes having a call relationship at the client side, or may be between two nodes having a call relationship at the server side.
According to the first, second and third schemes, after determining the node with the calling relationship in the interaction process of the client and the server, the target service node between two nodes with the calling relationship of the client can be determined, the target service node between two nodes with the calling relationship of the server can be determined, and the target service node between two nodes with the calling relationship corresponding to the client and the server can be determined at the same time. The above-mentioned execution steps are not limited to the embodiments of the present invention.
Further, according to two nodes with calling relations of the client and/or according to two nodes with calling relations of the server, determining the target service node, the following three schemes can be adopted:
scheme one: under the condition that the target service node is determined according to two nodes with calling relations of the client, the node without the calling relations can be screened out from the two nodes with the calling relations of the client, and then the node without the calling relations is determined as the target service node.
Scheme II: under the condition that the target service node is determined according to two nodes with calling relations of the server, the node without the calling relations can be screened out from the two nodes with the calling relations of the server, and then the node without the calling relations is determined to be the target service node.
Scheme III: under the condition that the target service node is determined according to two nodes with calling relations of the client and two nodes with calling relations of the server, the nodes without the calling relations can be respectively screened out from the two nodes with the calling relations of the client and the nodes without the calling relations can be screened out from the two nodes with the calling relations of the server, and then the nodes without the calling relations are determined to be the target service node.
It should be noted that, in the specific implementation process, the steps executed in the above scheme are not limited to the embodiment of the present invention.
In an exemplary embodiment, when the number of the target service nodes is multiple, the preset point location type is adopted to identify the target service nodes, and a mode of obtaining the preset buried point is specifically as follows:
step S40: screening target service nodes to be identified from a plurality of target service nodes;
step S42: and identifying the target service nodes to be identified according to the preset point location type, and obtaining preset buried points in the plurality of target service nodes.
In other words, the target service node to be identified needs to be screened from the plurality of target service nodes, then the target service node to be identified is identified according to the preset point location type, and finally the identified target service node to be identified is used as a preset buried point in the plurality of target service nodes. Through the implementation manner, the preset buried points needing to be identified can be screened from a plurality of target service nodes.
It should be noted that, in the case that the number of the target service nodes is one, the preset point location type may be used to identify the target service nodes, and the specific method for obtaining the preset buried point is as follows: and using the target service node as a target service node to be identified, and identifying the target service node to be identified according to a preset point location type to obtain a preset buried point corresponding to the target service node.
In an exemplary embodiment, determining the log of the target service node according to the preset buried point includes: recording parameter data of a target service node in a service execution process according to a preset buried point; and determining the parameter data as the log of the target service node.
Optionally, the parameter data of the target service node in the service execution process can be recorded by using the preset embedded point, and the parameter data is generated into the log of the target service node, that is, the log of the target service node contains the parameter data of the target service node in the service execution process recorded based on the preset embedded point.
In one exemplary embodiment, the above parameter data includes at least one of: the end time of service execution, the error code of service execution, the time spent on service execution, the number of reconnections of service execution.
It should be noted that the above parameter data includes, but is not limited to, an end time of service execution, an error code of service execution, a time spent for service execution, a number of reconnections of service execution, and the like. In addition, the timestamp can be used as an identifier in the service execution process, and the starting time, the ending time and the like of the service execution are recorded, so that the ending time, the spending time and the like of the service execution can be obtained; moreover, if the service execution is successful or not, a corresponding identifier can be adopted, for example, a 1 identifier can be adopted when the service execution is successful, a 0 identifier can be adopted when the service execution is failed, and then the identifier of the service execution failure can become an error code of the service execution; the number of reconnections of the service execution is the number of times of self-calling when the service is executed.
In an exemplary embodiment, after determining the log of the target service node, the method further includes: and calling a preset buried point corresponding to the target service node, and determining the problem of the target service node in the service execution process.
Because the preset embedded point records the parameter data corresponding to the node without the calling relation in the interaction process of the client and the server, the parameter data of the interface or the step without the interaction action can be analyzed by calling the preset embedded point corresponding to the target service node, so that the problem of the node in the service execution process can be obtained.
In order to better understand the process of the service node log processing method, the implementation method flow of the service node log processing is described below in conjunction with an alternative embodiment, but the implementation method flow is not limited to the technical scheme of the embodiment of the present invention.
In this embodiment, a method for processing a service node log is provided, and fig. 5 is a schematic diagram of a method for processing a service node log according to an embodiment of the present invention, as shown in fig. 5, specifically including the following steps:
step 1: a Client end (CS) Client initiates a request to generate a calling context;
step 2: receiving a request and generating a context by a Server Receiving (SR) Server;
step 3: the (DI) service end self-defines the data of interest of the embedded point;
step 4: the Server end (SS) Server returns a request result archiving context;
step 5: client Reagent (CR): the client receives a return result archive context.
In the implementation process of the step 1-5, the client context data may be reported by the client asynchronous queue, and the server context data may be reported by the server asynchronous queue.
It should be noted that, the DI refers to a log embedded point defined by the service end.
Further, the user is interested in making DI burial points; when the call relationship topological graph is drawn, the DI buried points can not be drawn, but can be searched out for a user to check the problem. The DI buried point can record information such as time, error code, time spent, reconnection times, etc. for checking problems or recording key information. The DI buried point can make up for the recording of interactive type points that are not realized due to technical constraints, thereby preserving feasibility for later technical improvements. In addition, the DI point location type is provided, and a buried point type system is perfected.
Through the embodiment, the target service node is obtained, wherein the target service node is a node which has no calling relationship in the interaction process of the client and the server; marking the target service node by adopting a preset point location type to obtain a preset buried point; and determining the log of the target service node according to the preset buried point. By adopting the technical scheme, the technical problem that the related information of the node without the calling relationship in the service execution process cannot be known in the related technology is solved, so that the interface or step without interactive behavior is recorded, and the technical effect of acquiring the related information of the node without the calling relationship in the service execution process is realized.
From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of the various embodiments of the present invention.
FIG. 6 is a block diagram of a processing device for service node logs according to an embodiment of the present invention; as shown in fig. 6, includes:
the obtaining module 62 is configured to obtain a target service node, where the target service node is a node that has no calling relationship in an interaction process between the client and the server;
it should be noted that, a node that does not have a call relationship in the process of interaction between the client and the server may be used as a target service node, where the target service node includes, but is not limited to, an interface or a step that does not have an interaction behavior in the process of interaction between the client and the server.
The identification module 64 is configured to identify a target service node by using a preset point location type, so as to obtain a preset buried point;
the preset point type may be a log embedded point customized by the service end or an embedded point other than CS, CR, SR, SS embedded point.
The determining module 66 is configured to determine a log of the target service node according to the preset buried point.
Optionally, the node without calling relation in the interaction process of the client and the server can be embedded by using the preset embedded point, so that the log of the node is obtained.
It should be noted that, the log includes parameter data of the target service node in the service execution process based on the preset embedded point record.
In an optional implementation manner, the client and the server are respectively provided with an asynchronous queue, wherein the asynchronous queue corresponding to the client is used for reporting the client context data in the interaction process of the client and the server, and the asynchronous queue corresponding to the server is used for reporting the server context data in the interaction process of the client and the server.
It should be noted that each of the above modules may be implemented by software or hardware, for example, in the latter case, it may be implemented by: the above modules may be located in the same processor; and/or the above modules are located in different processors in any combination.
It should be noted that, the acquiring module 62, the identifying module 64 and the determining module 66 correspond to steps S402 to S406 in the method embodiment, and the modules are the same as examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the method embodiment.
Through the embodiment, the target service node is obtained, wherein the target service node is a node which has no calling relationship in the interaction process of the client and the server; marking the target service node by adopting a preset point location type to obtain a preset buried point; and determining the log of the target service node according to the preset buried point. By adopting the technical scheme, the technical problem that the related information of the node without the calling relationship in the service execution process cannot be known in the related technology is solved, so that the interface or step without interactive behavior is recorded, and the technical effect of acquiring the related information of the node without the calling relationship in the service execution process is realized.
In one exemplary embodiment, the acquisition module 62 includes: the first determining unit is used for determining nodes with calling relations in the interaction process of the client and the server, wherein the client and the server are respectively provided with two nodes with calling relations; and the second determining unit is used for determining the target service node according to the two nodes with calling relations of the client and/or according to the two nodes with calling relations of the server.
After determining the node with the calling relation in the interaction process of the client and the server, the target service node between two nodes with the calling relation of the client can be determined, the target service node between two nodes with the calling relation of the server can be determined, and the target service node between two nodes with the calling relation respectively corresponding to the client and the server can be determined at the same time. The above-mentioned execution steps are not limited to the embodiments of the present invention.
In an exemplary embodiment, the second determining unit includes: a first determining subunit, configured to screen a node that does not have a calling relationship from between two nodes that have a calling relationship of the client, and determine the node that does not have a calling relationship as a target service node; and/or the second determining subunit is used for screening the node without the calling relationship from the two nodes with the calling relationship at the server side, and determining the node without the calling relationship as the target service node.
In an exemplary embodiment, when the number of the target service nodes is plural, the identification module 64 includes: the screening unit is used for screening target service nodes to be identified from the plurality of target service nodes; the identification unit is used for identifying the target service nodes to be identified according to the preset point location type to obtain preset buried points in the plurality of target service nodes.
It should be noted that, in the case that the number of the target service nodes is one, the preset point location type may be used to identify the target service nodes, and the specific method for obtaining the preset buried point is as follows: and using the target service node as a target service node to be identified, and identifying the target service node to be identified according to a preset point location type to obtain a preset buried point corresponding to the target service node.
In an exemplary embodiment, the determining module includes: the recording unit is used for recording parameter data of the target service node in the service execution process according to the preset buried point; and the third determining unit is used for determining the parameter data as the log of the target service node.
In one exemplary embodiment, the above parameter data includes at least one of: the end time of service execution, the error code of service execution, the time spent on service execution, the number of reconnections of service execution.
It should be noted that the above parameter data includes, but is not limited to, an end time of service execution, an error code of service execution, a time spent for service execution, a number of reconnections of service execution, and the like. In addition, the timestamp can be used as an identifier in the service execution process, and the starting time, the ending time and the like of the service execution are recorded, so that the ending time, the spending time and the like of the service execution can be obtained; moreover, if the service execution is successful or not, a corresponding identifier can be adopted, for example, a 1 identifier can be adopted when the service execution is successful, a 0 identifier can be adopted when the service execution is failed, and then the identifier of the service execution failure can become an error code of the service execution; the number of reconnections of the service execution is the number of times of self-calling when the service is executed.
In an exemplary embodiment, the above apparatus further includes: and the calling module is used for calling the preset buried point corresponding to the target service node after determining the log of the target service node, and determining the problem of the target service node in the service execution process.
Because the preset embedded point records the parameter data corresponding to the node without the calling relation in the interaction process of the client and the server, the parameter data of the interface or the step without the interaction action can be analyzed by calling the preset embedded point corresponding to the target service node, so that the problem of the node in the service execution process can be obtained.
An embodiment of the present invention also provides a storage medium including a stored program, wherein the program executes the method of any one of the above.
Alternatively, in the present embodiment, the above-described storage medium may be configured to store program code for performing the steps of:
s1, acquiring a target service node, wherein the target service node is a node which has no calling relation in the interaction process of a client and a server;
s2, marking the target service node by adopting a preset point location type to obtain a preset buried point;
s3, determining the log of the target service node according to the preset buried point.
An embodiment of the invention also provides an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.
Optionally, the electronic apparatus may further include a transmission device and an input/output device, where the transmission device is connected to the processor, and the input/output device is connected to the processor.
Alternatively, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:
s1, acquiring a target service node, wherein the target service node is a node which has no calling relation in the interaction process of a client and a server;
s2, marking the target service node by adopting a preset point location type to obtain a preset buried point;
s3, determining the log of the target service node according to the preset buried point.
Alternatively, in the present embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Alternatively, specific examples in this embodiment may refer to examples described in the foregoing embodiments and optional implementations, and this embodiment is not described herein.
It will be appreciated by those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a memory device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (9)
1. A method for processing a service node log, comprising:
obtaining a target service node, wherein the target service node is a node which has no calling relation in the interaction process of a client and a server;
marking the target service node by adopting a preset point location type to obtain a preset buried point;
determining the log of the target service node according to the preset buried point;
wherein obtaining the target service node includes:
determining nodes with calling relations in the interaction process of the client and the server, wherein the client and the server are respectively provided with two nodes with calling relations;
and determining the target service node according to the two nodes with calling relations of the client and/or according to the two nodes with calling relations of the server.
2. The method according to claim 1, wherein determining the target service node according to two nodes of the client having a call relationship and/or according to two nodes of the server having a call relationship comprises:
screening out nodes without calling relations from two nodes with calling relations of the client, and determining the nodes without calling relations as the target service nodes;
and/or the number of the groups of groups,
and screening out the nodes without calling relations from the two nodes with calling relations of the server, and determining the nodes without calling relations as the target service nodes.
3. The method of claim 1, wherein when the number of the target service nodes is plural, identifying the target service nodes by using a preset point location type to obtain a preset buried point, including:
screening out target service nodes to be identified from a plurality of target service nodes;
and identifying the target service node to be identified according to the preset point location type, and obtaining the preset buried points in the target service nodes.
4. The method of claim 1, wherein determining the log of the target service node based on the predetermined buried point comprises:
recording parameter data of the target service node in the service execution process according to the preset buried point;
and determining the parameter data as the log of the target service node.
5. The method of claim 4, wherein the parameter data comprises at least one of: the end time of service execution, the error code of service execution, the time spent on service execution, the number of reconnections of service execution.
6. The method according to any of claims 1 to 5, further comprising, after determining the log of the target service node:
and calling the preset buried point corresponding to the target service node, and determining the problem of the target service node in the service execution process.
7. A processing apparatus for a service node log, comprising:
the system comprises an acquisition module, a service server and a service server, wherein the acquisition module is used for acquiring a target service node, wherein the target service node is a node which does not have a calling relationship in the interaction process of the client and the service server;
the identification module is used for identifying the target service node by adopting a preset point location type to obtain a preset buried point;
the determining module is used for determining the log of the target service node according to the preset buried point;
the acquisition module comprises: the first determining unit is used for determining nodes with calling relations in the interaction process of the client and the server, wherein the client and the server are respectively provided with two nodes with calling relations; and the second determining unit is used for determining the target service node according to the two nodes with calling relations of the client and/or according to the two nodes with calling relations of the server.
8. A computer readable storage medium, characterized in that the computer readable storage medium comprises a stored program, wherein the program when run performs the method of any of the preceding claims 1 to 6.
9. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of the claims 1 to 6 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110701570.3A CN113434399B (en) | 2021-06-23 | 2021-06-23 | Service node log processing method and device, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110701570.3A CN113434399B (en) | 2021-06-23 | 2021-06-23 | Service node log processing method and device, storage medium and electronic device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113434399A CN113434399A (en) | 2021-09-24 |
| CN113434399B true CN113434399B (en) | 2023-06-16 |
Family
ID=77753696
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110701570.3A Active CN113434399B (en) | 2021-06-23 | 2021-06-23 | Service node log processing method and device, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113434399B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108156236A (en) * | 2017-12-22 | 2018-06-12 | 平安养老保险股份有限公司 | Service request processing method, device, computer equipment and storage medium |
| CN109542444A (en) * | 2017-07-31 | 2019-03-29 | 华为软件技术有限公司 | Monitoring method, device, server and the storage medium of JAVA application |
| CN109828750A (en) * | 2019-01-09 | 2019-05-31 | 西藏纳旺网络技术有限公司 | Auto-configuration data buries method, apparatus, electronic equipment and storage medium a little |
| CN111435298A (en) * | 2019-01-11 | 2020-07-21 | 北京京东尚科信息技术有限公司 | Point burying method and device, electronic equipment and storage medium |
| CN111858383A (en) * | 2020-07-31 | 2020-10-30 | 平安普惠企业管理有限公司 | Mobile APP data point burying method and system, terminal equipment and storage medium |
| CN112395180A (en) * | 2020-12-10 | 2021-02-23 | 南威软件股份有限公司 | Method for realizing service log full link tracking |
| CN112650963A (en) * | 2020-12-25 | 2021-04-13 | 北京达佳互联信息技术有限公司 | Webpage point burying method and device, electronic equipment and computer readable storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106656536B (en) * | 2015-11-03 | 2020-02-18 | 阿里巴巴集团控股有限公司 | Method and equipment for processing service calling information |
-
2021
- 2021-06-23 CN CN202110701570.3A patent/CN113434399B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109542444A (en) * | 2017-07-31 | 2019-03-29 | 华为软件技术有限公司 | Monitoring method, device, server and the storage medium of JAVA application |
| CN108156236A (en) * | 2017-12-22 | 2018-06-12 | 平安养老保险股份有限公司 | Service request processing method, device, computer equipment and storage medium |
| CN109828750A (en) * | 2019-01-09 | 2019-05-31 | 西藏纳旺网络技术有限公司 | Auto-configuration data buries method, apparatus, electronic equipment and storage medium a little |
| CN111435298A (en) * | 2019-01-11 | 2020-07-21 | 北京京东尚科信息技术有限公司 | Point burying method and device, electronic equipment and storage medium |
| CN111858383A (en) * | 2020-07-31 | 2020-10-30 | 平安普惠企业管理有限公司 | Mobile APP data point burying method and system, terminal equipment and storage medium |
| CN112395180A (en) * | 2020-12-10 | 2021-02-23 | 南威软件股份有限公司 | Method for realizing service log full link tracking |
| CN112650963A (en) * | 2020-12-25 | 2021-04-13 | 北京达佳互联信息技术有限公司 | Webpage point burying method and device, electronic equipment and computer readable storage medium |
Non-Patent Citations (2)
| Title |
|---|
| "LIANA: Live incremental time synchronization of traces for distributed systems analysis";Masoume Jabbarifar 等;《Journal of Network and Computer Applications》;第203-214页 * |
| "Web前端用户行为监测与分析平台的设计与实现";冯哲奇;《中国优秀硕士学位论文全文数据库信息科技辑》;第I139-88页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113434399A (en) | 2021-09-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108768752B (en) | Fault positioning method, device and system | |
| CN111831548B (en) | Dependency relationship topological graph drawing method and device | |
| CN105303112B (en) | The detection method and device of component call loophole | |
| CN111400127B (en) | Service log monitoring method and device, storage medium and computer equipment | |
| CN111176941A (en) | Data processing method, device and storage medium | |
| CN113434293A (en) | Method and apparatus for processing repeat request, storage medium, and electronic apparatus | |
| CN116204438A (en) | Test case generation method, automatic test method and related device | |
| CN105099769A (en) | Method, device and system for processing abnormal operations of service platform | |
| CN111353136A (en) | Method and device for processing operation request | |
| CN113434399B (en) | Service node log processing method and device, storage medium and electronic device | |
| CN112804099A (en) | Parameter batch configuration method and device, computer equipment and readable storage medium | |
| CN111008209B (en) | Data reconciliation method, device and system, storage medium and electronic device | |
| CN108647139B (en) | System test method, device, storage medium and electronic device | |
| CN115811484A (en) | Network detection method, device and storage medium | |
| CN112256658B (en) | Log record distribution method and device, storage medium and electronic device | |
| CN112650815B (en) | Method and device for synchronizing environment data, storage medium and electronic device | |
| CN115580647A (en) | Service call link tracking method and system and electronic equipment | |
| CN113934552A (en) | Method and device for determining function code, storage medium and electronic device | |
| CN113064814A (en) | Processing method and device of component reference data, storage medium and electronic device | |
| CN113434525A (en) | Cache data updating method and device, storage medium and electronic device | |
| CN112699009A (en) | Data detection method and device, server and storage medium | |
| CN111782291A (en) | Test page starting method and device | |
| CN113852919B (en) | Method and device for generating early warning message, storage medium and electronic device | |
| CN112799796A (en) | Timed task management method, device and storage medium | |
| CN113472808B (en) | Log processing method and device, storage medium and electronic device |
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 |