CN115883647A

CN115883647A - Service log recording method, system, device, terminal, server and medium

Info

Publication number: CN115883647A
Application number: CN202211515196.9A
Authority: CN
Inventors: 韩铭; 刘丹
Original assignee: Jingdong Technology Information Technology Co Ltd
Current assignee: Jingdong Technology Information Technology Co Ltd
Priority date: 2022-11-29
Filing date: 2022-11-29
Publication date: 2023-03-31

Abstract

The embodiment of the invention discloses a method, a system, a device, a terminal, a server and a medium for recording service logs. The method is applied to the client and can comprise the following steps: responding to the first request intercepting instruction, acquiring the intercepted service request, and obtaining log data generated under the condition that the service function corresponding to the service request is triggered; fusing log data and a service request to obtain a log request; and sending the log request to the server side so that the server side obtains log data from the intercepted log request, and fusing the log data and a response result corresponding to the intercepted log request to obtain a service log so as to record the service log. According to the technical scheme of the embodiment of the invention, the log data is quickly and accurately acquired by means of the intuitive perception of the front end on the log data, so that the recording efficiency and accuracy of the service log are ensured.

Description

Service log recording method, system, device, terminal, server and medium

Technical Field

The embodiment of the invention relates to the technical field of computer application, in particular to a method, a system, a device, a terminal, a server and a medium for recording service logs.

Background

The service log is generally a log used for recording detailed operations of a user of a certain service platform on a key service function in the service platform, and a recording process of the service log is currently realized through a back end.

In the process of implementing the present invention, the inventor finds that the following technical problems exist in the prior art: it is difficult to ensure the recording efficiency and accuracy of the service log.

Disclosure of Invention

The embodiment of the invention provides a method, a system, a device, a terminal, a server and a medium for recording a service log, so as to realize the effect of efficiently and accurately recording the service log.

According to an aspect of the present invention, a method for logging a service is provided, where the method is applied to a client, and the method may include:

responding to the first request intercepting instruction, acquiring the intercepted service request, and obtaining log data generated under the condition that the service function corresponding to the service request is triggered;

fusing log data and a service request to obtain a log request;

and sending the log request to the server so that the server obtains log data from the intercepted log request, and fusing the log data and a response result corresponding to the intercepted log request to obtain a service log so as to record the service log.

According to another aspect of the present invention, a method for logging a service is provided, where the method is applied to a server, and the method may include:

responding to the second request intercepting instruction, acquiring the intercepted log request containing the log data, and obtaining the log data from the log request;

acquiring a response result corresponding to the intercepted log request, and fusing log data and the response result to obtain a service log so as to record the service log;

the log request is a request obtained by fusing log data and a service request, and the log data is data generated under the condition that a service function corresponding to the service request is triggered.

According to another aspect of the present invention, a service logging system is provided, which may include a client and a server; wherein, the first and the second end of the pipe are connected with each other,

the client is used for responding to the first request intercepting instruction, acquiring the intercepted service request, acquiring log data generated under the condition that the service function corresponding to the service request is triggered, and transmitting the log request acquired by fusing the log data and the service request to the server;

and the server is used for responding to the second request intercepting instruction, acquiring the intercepted log request, acquiring log data from the log request, and fusing a response result corresponding to the intercepted log request and the log data to obtain a service log so as to record the service log.

According to another aspect of the present invention, there is provided a service logging apparatus configured at a client, the apparatus may include:

the log data first obtaining module is used for responding to the first request intercepting instruction, obtaining the intercepted service request and obtaining the log data generated under the condition that the service function corresponding to the service request is triggered;

the log request obtaining module is used for fusing log data and the service request to obtain a log request;

and the first recording module of the service log is used for sending the log request to the server so that the server obtains log data from the intercepted log request, and fusing the log data and a response result corresponding to the intercepted log request to obtain the service log so as to record the service log.

According to another aspect of the present invention, there is provided a service logging apparatus configured at a server, the apparatus may include:

the second log data obtaining module is used for responding to the second request intercepting instruction, obtaining the intercepted log request containing the log data and obtaining the log data from the log request;

the second business log recording module is used for acquiring a response result corresponding to the intercepted log request, and fusing log data and the response result to obtain a business log so as to record the business log;

According to another aspect of the present invention, there is provided a terminal, which may include:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to cause the at least one processor to perform a method of service logging provided by any of the embodiments of the present invention when executed.

According to another aspect of the present invention, there is provided a server, which may include:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,

According to another aspect of the present invention, there is provided a computer-readable storage medium having stored thereon computer instructions for causing a processor to execute a method of logging traffic provided by any of the embodiments of the present invention.

According to the technical scheme of the embodiment of the invention, the intercepted service request is obtained by responding to the first request intercepting instruction, the log data generated under the condition that the service function corresponding to the service request is triggered is obtained, and the log data is directly acquired and not obtained by analyzing the response result, so that the acquisition efficiency and accuracy of the log data are ensured; further, the log data and the service request are fused to obtain a log request carrying the log data; and sending the log data to the server along with the log request so that the server obtains the log data from the intercepted log request, and fusing the log data and a response result corresponding to the intercepted log request to obtain a service log so as to realize the recording function of the service log. According to the technical scheme, the log data are quickly and accurately acquired by means of visual perception of the front end on the log data, so that the recording efficiency and accuracy of the service log are ensured, the complexity of a service platform is not increased in the recording process of the service log, the normal service process is not interfered, and the maintainability is good.

It should be understood that the statements in this section do not necessarily identify key or critical features of any embodiment of the present invention, nor do they necessarily limit the scope of the present invention. Other features of the present invention will become apparent from the following description.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a flowchart of a method for logging a service according to an embodiment of the present invention;

FIG. 2 is a flow chart of another method for service logging provided by an embodiment of the invention;

FIG. 3 is a flow chart of another method for service logging provided by an embodiment of the invention;

FIG. 4 is a block diagram of a service logging system according to an embodiment of the present invention;

FIG. 5 is a schematic diagram providing an alternative example of a traffic logging system according to an embodiment of the present invention;

fig. 6 is a block diagram illustrating a structure of a service logging apparatus according to an embodiment of the present invention;

FIG. 7 is a block diagram of another embodiment of a service logging device

Fig. 8 is a schematic structural diagram of an electronic device implementing the service logging method according to the embodiment of the present invention.

Detailed Description

In order to make those skilled in the art better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. The cases of "target", "original", etc. are similar and will not be described in detail 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.

In order to better understand how the service log recording method described in the embodiment of the present invention efficiently and accurately records the service log without increasing the complexity of the service platform, an exemplary description will be given below of a recording process for realizing the service log through a back end, which is described in the background art. Illustratively, taking an example that the Service platform is a Software-as-a-Service (SAAS) platform, the SAAS platform has product services 1, product services 2 and gateway services accessed thereon, and each product Service corresponds to a respective Service function (i.e., the product Service may be considered to be deployed on a server, and the corresponding Service function may be considered to be deployed on a terminal). Taking the process of realizing the recording of the service log by the gateway service, as an example, after receiving a service request sent by the front end and generated because a certain service function is triggered, the gateway service forwards the service request to the corresponding product service, and after intercepting a response result returned by the product service, first determines whether the service log corresponding to the response result needs to be recorded, and if so, analyzes the response result, thereby obtaining what the service log corresponding to the response result is, so as to record the service log.

However, it is time-consuming to analyze the response result, so that it is difficult to ensure the recording efficiency of the service log. In addition, for the case that the service log needs to record data change before and after the service function is triggered, if the service function is a delete function, the service log needs to record a delete operation, a response result of the delete operation, and deleted data (i.e., log data related to the service log), at this time, it is difficult to obtain accurate deleted data by directly analyzing the response result, so that it is difficult to ensure the recording accuracy of the service log. It should be noted that, if, in order to ensure the recording accuracy, an inquiry service (i.e., a business code that can implement an inquiry function is embedded in the gateway service) may be deployed in the gateway service to inquire about the deleted data, but this may increase the complexity of the business platform, and here, the deleted data may be inquired if the invoking process of the inquiry service needs to be performed before the invoking process of the deletion service, which may affect the normal business process.

Fig. 1 is a flowchart of a method for logging a service provided in an embodiment of the present invention. The embodiment is applicable to the case of recording the service log, and is particularly applicable to the case of acquiring log data through a front end (namely a client) and then realizing the recording process of the service log corresponding to the log data through a back end (namely a server). The method can be executed by the service logging device provided by the embodiment of the invention, the device can be realized by software and/or hardware, and the device can be integrated on a terminal.

Referring to fig. 1, the method of the embodiment of the present invention specifically includes the following steps:

s110, responding to the first request intercepting instruction, obtaining the intercepted service request, and obtaining the log data generated under the condition that the service function corresponding to the service request is triggered.

The first request intercepting instruction may be an instruction for intercepting a service request, and the service request may be any one of requests deployed on the terminal or a request generated when a service function requiring a service log record is triggered and used for requesting to invoke a product service corresponding to the service function deployed on the server. And intercepting the service request in response to the first request interception instruction. In practical application, optionally, the intercepting action may be implemented based on a first request interceptor deployed on the terminal, where the first request interceptor may be respectively deployed in a service code corresponding to each service function that has a service log record requirement, so as to intercept a service request corresponding to the service function that has the service log record requirement; or a uniform request interceptor deployed on the terminal, so as to intercept the service request corresponding to any service function. Compared with the former, the latter has better universality and lightens the invasion of the business logging function to the business function.

The log data may be data related to the service log generated in a case where a service function corresponding to the intercepted service request is triggered, and for example, when the service function is a delete function, the log data may be deleted data; when the business function is a modify function, the log data may be pre-modified data and post-modified data. After the service request is intercepted, if log data corresponding to the service request can be obtained, which indicates that a service function corresponding to the service request has a service log recording requirement, the subsequent steps can be continuously executed; otherwise, it is indicated that the service function corresponding to the service request does not have a service log recording requirement, and the service request can be directly sent to the server, so that the server processes the service request.

It should be noted that, compared to the example of obtaining log data by analyzing the response result set forth above, the embodiment of the present invention directly collects log data from a production end (i.e., a front end) of the log data, thereby ensuring the efficiency and accuracy of obtaining the log data. Moreover, log data, which is an important component in the service log, is rapidly and accurately acquired, and is very important for recording efficiency and accuracy of the service log.

And S120, fusing the log data and the service request to obtain a log request.

The service request sent by the service code carries service data, but not log data, so that the service request is intercepted before being sent to the server, the obtained log data is fused with the service request to obtain the log request carrying the log data, and the log data is sent to the server along with the log request. In practical applications, optionally, the service data and the log data may be completely the same, partially the same, or completely different data, which is not limited herein.

S130, the log request is sent to the server side, so that the server side obtains log data from the intercepted log request, and response results corresponding to the log data and the intercepted log request are fused to obtain a service log, so that the service log is recorded.

And sending the log request carrying the log data to a server. On the basis, the server can intercept the log request and then obtain log data from the log request, and the interception action can be realized based on a second request interceptor deployed on the server; moreover, the server can send the log request to the corresponding product service and intercept the response result returned by the product service for the log request, and this interception can be implemented based on a response interceptor deployed on the server. Furthermore, the server can fuse the log data and the response result to obtain the service log, thereby realizing the recording function of the service log.

According to the technical scheme of the embodiment of the invention, the intercepted service request is obtained by responding to the first request intercepting instruction, and the log data generated under the condition that the service function corresponding to the service request is triggered is obtained, wherein the log data is directly acquired and is not obtained by analyzing the response result, so that the obtaining efficiency and accuracy of the log data are ensured; further, the log data and the service request are fused to obtain a log request carrying the log data; and sending the log data to the server along with the log request so that the server obtains the log data from the intercepted log request, and fusing the log data and a response result corresponding to the intercepted log request to obtain a service log so as to realize the recording function of the service log. According to the technical scheme, the log data are quickly and accurately acquired by means of visual perception of the front end on the log data, so that the recording efficiency and accuracy of the service log are ensured, the complexity of a service platform is not increased in the recording process of the service log, the normal service process is not interfered, and the maintainability is good.

An optional technical solution, fusing log data and a service request to obtain a log request, may include: storing the log data into a request header of a service request to obtain a log request; so that the server obtains log data from the intercepted log request, which may include: so that the server side obtains the log data from the request header of the intercepted log request. The client side obtains the log request carrying the log data by storing the log data into a request header (header) of the service request. Furthermore, after intercepting the log request, the server can obtain log data from the request header of the log request, thereby achieving the effect of fast and accurate transmission of the log data. In practical applications, optionally, the client may encode the log data first, and then store the encoded log data in the request header. Then, after obtaining the log data from the log request, the server may decode the log data first, and then perform subsequent steps based on the decoded log data.

Before the embodiments of the present invention are described, an application scenario of the embodiments of the present invention is described as an example. The service log recording process is a recording process as required, that is, only the service log corresponding to the service function having the service log recording requirement needs to be recorded. Therefore, the first request interceptor can be deployed in the service code corresponding to the corresponding service function according to the recording requirement, so as to intercept the service request corresponding to the service function. However, this causes a serious coupling between the service code and the service logging code, and is highly invasive, thereby causing a problem that the code is difficult to maintain. Alternatively, the intrusiveness can be reduced to a certain extent by deploying a uniform first request interceptor, but this requires that a large function blacklist is preset in the first request interceptor, thereby filtering out service requests corresponding to service functions that do not need to record a service log. However, the service function that needs to record the service log may be adjusted at any time, which means that the function blacklist in the first request interceptor also needs to be modified and issued at any time, and the service adaptability is poor, so that the stability of the service platform is easily affected. To this end, a traffic logging method set forth in the following embodiments is proposed.

Fig. 2 is a flowchart of another service logging method provided in the embodiment of the present invention. The present embodiment is optimized based on the above technical solutions. In this embodiment, optionally, the log data is processed through the following steps: responding to the trigger operation aiming at the service function, if a service log embedded point script related to the service function exists, acquiring log data, and transmitting the log data to the service log embedded point script so as to store the log data in a first cache; obtaining log data generated when the service function corresponding to the service request is triggered may include: and if the first cache stores the log data generated under the condition that the service function corresponding to the service request is triggered, obtaining the log data from the first cache. The same or corresponding terms as those in the above embodiments are not explained in detail herein.

Referring to fig. 2, the method of the present embodiment may specifically include the following steps:

s210, responding to the triggering operation aiming at the service function, if the service log embedded point script associated with the service function exists, obtaining the log data generated under the condition that the service function is triggered, and transmitting the log data to the service log embedded point script so as to store the log data in a first cache.

The triggering operation may be an operation performed to trigger a certain service function, such as a click operation, a press operation, or a slide operation, which is not specifically limited herein. In response to the triggering operation, determining whether a service log buried point script associated with the triggered service function exists, wherein the service log buried point script can be understood as a script which is embedded in a service code corresponding to the service function with the service log recording requirement in advance. Therefore, if the log data exists, which indicates that the service function has a service log recording requirement, the log data generated in the case that the service function is triggered can be acquired, and the log data is transferred to the service log buried point script, so that the log data can be stored in the first cache by executing the service log buried point script. In practical application, optionally, the service log embedded point script has a function of storing log data, so that the service log embedded point script embedded in each service code has universality.

And S220, sending a service request corresponding to the trigger operation.

It should be noted that S210-S220 and subsequent S230-S260 may be executed by the same client, or may be executed by different clients (for example, the former is executed by a service client implementing a service function, the latter is executed by a service logging client implementing a service logging function, and the two clients may be located on the same terminal), which is not specifically limited herein.

And S230, responding to the first request intercepting instruction, and acquiring the intercepted service request.

S240, if the log data corresponding to the service request is stored in the first cache, obtaining the log data from the first cache.

After a certain service request is intercepted, if log data corresponding to the service request is stored in the first cache, which indicates that a service function corresponding to the service request has a service log recording requirement, the log data can be obtained from the first cache so as to be matched with the subsequent steps, the log data is sent to the server, a service log corresponding to the log data is generated, and then the recording function of the service log is realized.

And S250, fusing the log data and the service request to obtain a log request.

And S260, sending the log request to the server so that the server obtains log data from the intercepted log request, and fusing the log data and a response result corresponding to the intercepted log request to obtain a service log so as to record the service log.

It should be noted that, in the above technical solution, whether the service function corresponding to the intercepted service request has a service log recording requirement can be determined by whether log data is stored in the first cache, so that the first request interceptor set here can be a uniform request interceptor, thereby implementing decoupling between the service code and the service log recording code, and solving the problem that the code is difficult to maintain; moreover, a large number of function blacklists do not need to be preset in the first request interceptor, which means that when the service function with the service log recording requirement changes, the first request interceptor does not need to be modified, and the service adaptability is good, so that the stability of the service platform is ensured.

In addition, the service function is usually a function which can be seen and touched in the front end, so when the service function changes, related personnel can quickly determine whether the service log recording requirement of the related personnel needs to change, and when the service log recording requirement needs to change, the acquisition action (namely whether acquisition is carried out) of corresponding log data is adjusted by adding or deleting corresponding embedded points (namely service log embedded point scripts), so that the service log recording can quickly sense the change of the service function and further quickly carry out adaptation adjustment, thereby avoiding the condition of service log recording error or failure caused by the change of the service function, and ensuring the maintainability of the service log recording function.

According to the technical scheme of the embodiment of the invention, the service log embedded point script is associated with the service function needing to record the service log in advance, and then the log data generated when the service function is triggered is stored by executing the service log embedded point script, so that the corresponding service log is recorded by obtaining the stored log data. The technical scheme solves the problems that codes are difficult to maintain due to code coupling and the stability of the service platform is poor due to frequent modification and issuance of the first request interceptor.

Fig. 3 is a flowchart of a service logging method provided in an embodiment of the present invention. The embodiment is applicable to the case of recording the service log, and is particularly applicable to the case of acquiring log data through a front end (namely a client) and then realizing the recording process of the service log corresponding to the log data through a back end (namely a server). The method can be executed by the service logging device provided by the embodiment of the invention, the device can be realized by software and/or hardware, and the device can be integrated on a server.

Referring to fig. 3, the method of this embodiment may specifically include the following steps:

s310, responding to the second request intercepting instruction, obtaining the intercepted log request containing the log data, and obtaining the log data from the log request, wherein the log request is obtained by fusing the log data and the service request, and the log data is generated under the condition that the service function corresponding to the service request is triggered.

The second request intercepting instruction may be an instruction for intercepting a request (referred to as an intercepted request herein) sent by the client, where the intercepted request may be a service request not carrying log data or a log request carrying log data, which is related to an actual situation and is not specifically limited herein. And responding to the second request interception instruction, and obtaining log data from the log request aiming at the intercepted log request. In practical applications, optionally, the above intercepting action may be implemented based on a second request interceptor deployed on the server side, so as to intercept each intercepted request sent by the residential client. On this basis, optionally, the second request interceptor may be deployed on a gateway service, and the gateway service may be deployed on a server, so that the effects of both request interception and request forwarding (i.e., forwarding to a corresponding product service) are achieved by the gateway service.

On this basis, optionally, obtaining the intercepted log request including the log data, and obtaining the log data from the log request may include: acquiring an intercepted request, and determining whether the intercepted request contains log data; if yes, the intercepted request is used as a log request, and log data are obtained from the log request. As described above, the intercepted request may be a service request or a log request, and therefore, after the intercepted request is obtained, it may be determined whether log data is included therein. If yes, the intercepted request is a log request, and log data can be obtained from the intercepted request; otherwise, this indicates that the intercepted request is a business request, and it can be directly forwarded to the corresponding product service.

S320, acquiring a response result corresponding to the intercepted log request, and fusing the log data and the response result to obtain a service log so as to record the service log.

After obtaining the log data from the log request, the log request may be forwarded to a product service that can process the log request, and a response result returned by the product service for the log request is intercepted, which may be implemented based on a response interceptor deployed on the service end. Because the log data and the response result are important components in the service log, the log data and the response result are fused to obtain the service log, so that the recording function of the service log is realized.

On this basis, optionally, to record the service log, may include: and sending the recording request corresponding to the service log to a service log service so as to store the service log into a database corresponding to the service log service to record the service log. The recording request may be a request for recording a service log, and the service log service may be a service that can implement a service log recording function. The recording request is forwarded to the service log service, so that the service log is stored in the database corresponding to the service log service based on the service log service, and the effect of effective recording of the service log is achieved. On the basis, optionally, the process of forwarding the recording request to the service log service can be understood as a process of calling an interface corresponding to the service log service based on the recording request, and the calling process can be an asynchronous calling process.

In addition, it should be noted that other technical features not described in the embodiments of the present invention have been described in detail in the foregoing embodiments, and are not described herein again.

According to the technical scheme of the embodiment of the invention, the intercepted log request is obtained by responding to the second request intercepting instruction, the log request is obtained by fusing the log data and the service request, so that the log data can be obtained from the log request, and the log data is generated under the condition that the service function corresponding to the service request is triggered; and further, acquiring a response result corresponding to the intercepted log request, and fusing the log data and the response result to obtain a service log so as to record the service log. According to the technical scheme, the log data are directly acquired from the log request and are not acquired after the response result is analyzed, so that the log data are quickly and accurately acquired, the recording efficiency and accuracy of the service log are further ensured, the complexity of the service platform is not increased in the recording process of the service log, the normal service process is not interfered, and the maintainability is good.

An optional technical solution, after obtaining log data from a log request, the service log recording method may further include: storing the log data into a second cache; fusing the log data with the response result may include: if the log data corresponding to the response result are stored in the second cache, obtaining the log data corresponding to the response result from the second cache; and fusing the response result and the log data corresponding to the response result. After intercepting a response result returned by any product service, since a business function corresponding to the product service may or may not have a business logging requirement, it may be determined whether log data corresponding to the response result exists in the second cache. If the service function corresponding to the product service has the service log recording requirement, the log data corresponding to the response result can be obtained from the second cache, and then the response result and the obtained log data are fused, so that the accuracy of the subsequently generated service log is ensured.

Fig. 4 is a block diagram of a service logging system according to an embodiment of the present invention. Referring to fig. 4, the traffic logging system may include a client 410 and a server 420; the client 410 is configured to, in response to the first request intercepting instruction, acquire an intercepted service request, acquire log data generated when a service function corresponding to the service request is triggered, and send the log request acquired by fusing the log data and the service request to the server 420; the server 420 is configured to respond to the second request intercepting instruction, obtain the intercepted log request, obtain log data from the log request, and fuse a response result corresponding to the intercepted log request with the log data to obtain a service log, so as to record the service log.

It should be noted that specific implementation processes of the client 410 and the server 420 and other implementation processes have been described in detail in the foregoing embodiments, and are not described herein again.

The service log recording system ensures the recording efficiency and accuracy of the service log by the mutual matching of the client and the service end, does not increase the complexity of the service platform and interfere the normal service process in the service log recording process, and has better maintainability.

In order to better understand the implementation process of the service logging system as a whole, it is exemplified below with reference to specific examples. Illustratively, as shown in fig. 5, here, the SAAS platform in the above example is still taken as an example, specifically:

1. aiming at a service function with a service log recording requirement, a service log embedded point script is deployed under a service code corresponding to the service function in advance, and the service log embedded point script can also be called a service log embedded point SDK (Software Development Kit), and can be used for storing log data into a first cache. On the basis, when the service function with the service log embedded point SDK is operated by a user, the log data generated when the service function is operated by the user is transmitted to the corresponding service log embedded point SDK, so that the log data is stored in the first cache through the service log embedded point SDK. Illustratively, the log data may be data related to the operation module, the operation type, and the operation details. Then, a service request corresponding to the service function is sent to the back end. In addition, when the service function which is not deployed with the service log embedded point SDK is operated by the user, the service request corresponding to the service function can be directly sent to the back end.

2. And a first request interceptor is deployed at the front end and used for uniformly intercepting the service request for calling the back-end interface. After the service request is intercepted, it may be determined whether log data corresponding to the service request is stored in the first cache. If the service function corresponding to the service request has a service log recording requirement, the log data corresponding to the service request can be taken out from the first cache, and the log data is coded and signed and then is put into the header of the service request to obtain a log request, and the log request is sent to the gateway service. Of course, for a service request in which corresponding log data is not stored in the first cache, the service request may be directly sent to the gateway service.

3. And a second request interceptor is deployed on the gateway service and used for uniformly intercepting intercepted requests sent by the client. For an intercepted request, it may be determined whether there is encoded signed log data in the header of the intercepted request. If so, indicating that the intercepted request is a log request, the encoded and signed log data may be obtained from the header of the log request, decoded, stored in the second cache, and forwarded to the production service that may process the log request. Otherwise, this indicates that the intercepted request is a service request, and the service request can be directly forwarded to a product service that can process the service request. Furthermore, a response interceptor is deployed on the gateway service and used for uniformly intercepting response results returned by the product service. After the response result is intercepted, it may be determined whether log data corresponding to the response result is stored in the second cache. If the service function corresponding to the response result has the service log recording requirement, the log data corresponding to the response result can be obtained from the second cache, and the obtained log data and the intercepted response result are combined to obtain the service log. In practical applications, the service log may be represented by a service log recording parameter. And asynchronously calling an interface of the service log service based on the service log recording parameter.

4. And the independent service log service is used for recording the service log. Specifically, when the interface of the service log service is called, the corresponding service log can be stored in a storage, so that the service log recording function is realized. Moreover, the service log service can also provide an interface for querying, so that the user can query the service log.

Therefore, in the whole process, except for embedding the service log embedded point SDK into the service code, the execution process of any service process cannot be influenced by other front-end and back-end interception operations, so that the independent stability of the core process is ensured. By applying the service log embedded point SDK, when the recording requirement of the service log changes, related personnel can immediately evaluate whether to adjust some service log embedded point SDKs, the service log record is ensured to be modified along with the change of the requirement, and the maintainability of the service log recording function is further ensured. In addition, the service request/log request is subjected to tangent plane processing through the request interceptors at the front end and the back end, and asynchronous service log storage is added, so that service log recording can be completed without invading the original service code, and the functional modules are completely independent in design, thereby facilitating the expansion of other similar service scenes.

Fig. 6 is a block diagram of a service logging apparatus provided in an embodiment of the present invention, where the apparatus is configured to execute a service logging method provided in any of the above embodiments. The device and the service log recording method of each embodiment belong to the same inventive concept, and details which are not described in detail in the embodiment of the service log recording device can refer to the embodiment of the service log recording method. As shown in fig. 6, the apparatus configured at the client specifically includes: a first log data obtaining module 510, a log request obtaining module 520 and a first service log recording module 530. Wherein the content of the first and second substances,

a log data first obtaining module 510, configured to respond to the first request intercepting instruction, obtain an intercepted service request, and obtain log data generated when a service function corresponding to the service request is triggered;

a log request obtaining module 520, configured to fuse log data and a service request to obtain a log request;

the first recording module 530 of the service log is configured to send a log request to the server, so that the server obtains log data from the intercepted log request, and fuses the log data and a response result corresponding to the intercepted log request to obtain the service log, so as to record the service log.

Optionally, the log request obtaining module 520 may specifically be configured to:

storing the log data into a request header of a service request to obtain a log request;

the first logging module 530 of the service log may include:

and the log data first obtaining unit is used for enabling the server to obtain the log data from the request header of the intercepted log request.

Optionally, the log data is processed by the following modules:

the log data storage module is used for responding to triggering operation aiming at the service function, if a service log embedded point script related to the service function exists, obtaining log data, and transmitting the log data to the service log embedded point script so as to store the log data in a first cache;

the log data first obtaining module 510 may include:

and the second log data obtaining unit is used for obtaining the log data from the first cache if the log data generated under the condition that the service function corresponding to the service request is triggered is stored in the first cache.

According to the service log recording device provided by the embodiment of the invention, the log data first obtaining module responds to the first request intercepting instruction to obtain the intercepted service request, so that the log data generated under the condition that the service function corresponding to the service request is triggered is obtained, the log data is directly acquired and is not obtained by analyzing the response result, and thus the obtaining efficiency and accuracy of the log data are ensured; further, the log data and the service request are fused through a log request obtaining module to obtain a log request carrying the log data; and sending the log data to the server side along with the log request through the first recording module of the service log so that the server side obtains the log data from the intercepted log request, and fusing the log data and a response result corresponding to the intercepted log request to obtain the service log so as to realize the recording function of the service log. According to the device, the log data are quickly and accurately acquired by means of visual perception of the front end on the log data, so that the recording efficiency and accuracy of the service log are ensured, the complexity of a service platform is not increased in the recording process of the service log, the normal service process is not interfered, and the maintainability is good.

The service log recording device provided by the embodiment of the invention can execute the service log recording method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

It should be noted that, in the embodiment of the service log recording apparatus, each unit and each module included in the embodiment are only divided according to functional logic, but are not limited to the above division, as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.

Fig. 7 is a block diagram of a service logging apparatus provided in an embodiment of the present invention, where the apparatus is configured to execute a service logging method provided in any of the above embodiments. The device and the service log recording method of each embodiment belong to the same inventive concept, and details that are not described in detail in the embodiment of the service log recording device can refer to the embodiment of the service log recording method. As shown in fig. 7, the apparatus is configured at the server, and may specifically include: a second log data obtaining module 610 and a second service log recording module 620.

The log data second obtaining module 610 is configured to, in response to the second request intercepting instruction, obtain an intercepted log request that includes log data, and obtain the log data from the log request;

a second service log recording module 620, configured to obtain a response result corresponding to the intercepted log request, and fuse the log data and the response result to obtain a service log, so as to record the service log;

Optionally, the second obtaining module 610 for log data may include:

the log data determining unit is used for acquiring the intercepted request and determining whether the intercepted request contains log data;

and a third obtaining unit of log data, which is used for obtaining the log data from the log request by taking the intercepted request as the log request if the intercepted request is the log request.

Optionally, the service log recording apparatus may further include:

the log data storage module is used for storing the log data into a second cache after the log data are obtained from the log request;

the second recording module 620 of the service log may include:

the log data acquisition unit is used for acquiring the log data corresponding to the response result from the second cache if the log data corresponding to the response result is stored in the second cache;

and the fusion unit is used for fusing the response result and the log data corresponding to the response result.

Optionally, the second recording module 620 of the service log may include:

and the business log recording unit is used for sending the recording request corresponding to the business log service so as to store the business log into a database corresponding to the business log service to record the business log.

In the service log recording apparatus provided in the embodiment of the present invention, the log data second obtaining module responds to the second request intercepting instruction to obtain the intercepted log request, where the log request is a request obtained by fusing the log data and the service request, and therefore the log data can be obtained from the log request, and the log data is data generated when the service function corresponding to the service request is triggered; further, a response result corresponding to the intercepted log request is obtained through a second recording module of the service log, and the log data and the response result are fused to obtain the service log so as to record the service log. According to the device, the log data are directly obtained from the log request and are not obtained after the response result is analyzed, so that the log data are quickly and accurately obtained, the recording efficiency and accuracy of the service log are further ensured, the complexity of the service platform is not increased in the recording process of the service log, the normal service process is not interfered, and the maintainability is good.

The service log recording device provided by the embodiment of the invention can execute the service log recording method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.

Fig. 8 shows a schematic structural diagram of an electronic device (e.g., the terminal or the server in fig. 8) 10 that can be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 8, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to the bus 14.

A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 performs the various methods and processes described above, such as the traffic logging method.

In some embodiments, the traffic logging method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the traffic logging method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the traffic logging method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the Internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.

The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for recording service logs is applied to a client, and the method comprises the following steps:

responding to a first request intercepting instruction, acquiring an intercepted service request, and acquiring log data generated under the condition that a service function corresponding to the service request is triggered;

fusing the log data and the service request to obtain a log request;

and sending the log request to a server so that the server obtains the log data from the intercepted log request, and fusing the log data and a response result corresponding to the intercepted log request to obtain a service log so as to record the service log.

2. The method of claim 1, wherein the merging the log data with the service request to obtain a log request comprises:

storing the log data into a request header of the service request to obtain a log request;

the obtaining, by the server, the log data from the intercepted log request includes:

and the server side obtains the log data from the request header of the intercepted log request.

3. The method of claim 1, wherein the log data is processed by:

responding to the triggering operation aiming at the service function, if a service log embedded point script related to the service function exists, acquiring the log data, and transmitting the log data to the service log embedded point script so as to store the log data in a first cache;

the obtaining of the log data generated under the condition that the service function corresponding to the service request is triggered includes:

and if the log data generated under the condition that the service function corresponding to the service request is triggered is stored in the first cache, obtaining the log data from the first cache.

4. A method for recording service logs is applied to a server side, and the method comprises the following steps:

responding to a second request intercepting instruction, acquiring an intercepted log request containing log data, and obtaining the log data from the log request;

acquiring a response result corresponding to the intercepted log request, and fusing the log data and the response result to obtain a service log so as to record the service log;

the log request is a request obtained by fusing the log data and the service request, and the log data is data generated under the condition that the service function corresponding to the service request is triggered.

5. The method of claim 4, wherein obtaining the intercepted log request containing the log data and obtaining the log data from the log request comprises:

acquiring an intercepted request, and determining whether the intercepted request contains log data;

if yes, the intercepted request is used as a log request, and the log data is obtained from the log request.

6. The method of claim 4, further comprising, after said obtaining the log data from the log request:

storing the log data in a second cache;

the fusing the log data and the response result comprises:

if the log data corresponding to the response result is stored in the second cache, the log data corresponding to the response result is obtained from the second cache;

and fusing the response result and the log data corresponding to the response result.

7. The method of claim 4, wherein the recording the traffic log comprises:

and sending a recording request corresponding to the service log to a service log service so as to store the service log in a database corresponding to the service log service to record the service log.

8. A service log recording system is characterized by comprising a client and a server; wherein the content of the first and second substances,

the client is used for responding to a first request intercepting instruction, acquiring an intercepted service request, acquiring log data generated under the condition that a service function corresponding to the service request is triggered, and transmitting the log request acquired after the log data and the service request are fused to the server;

the server is used for responding to a second request intercepting instruction, acquiring the intercepted log request, obtaining the log data from the log request, and fusing a response result corresponding to the intercepted log request and the log data to obtain a service log so as to record the service log.

9. A service logging device, configured at a client, the device comprising:

the first log data acquisition module is used for responding to a first request interception instruction, acquiring an intercepted service request and acquiring log data generated under the condition that a service function corresponding to the service request is triggered;

a log request obtaining module, configured to fuse the log data and the service request to obtain a log request;

and the first business log recording module is used for sending the log request to a server so that the server obtains the log data from the intercepted log request, and fusing the log data and a response result corresponding to the intercepted log request to obtain a business log so as to record the business log.

10. A service logging device, configured at a server, the device comprising:

a second log data obtaining module, configured to respond to a second request intercepting instruction, obtain an intercepted log request including log data, and obtain the log data from the log request;

the second business log recording module is used for acquiring a response result corresponding to the intercepted log request, and fusing the log data and the response result to obtain a business log so as to record the business log;

11. A terminal, comprising:

at least one processor; and

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to cause the at least one processor to perform the traffic logging method of any of claims 1-3.

12. A server, comprising:

at least one processor; and

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to cause the at least one processor to perform the traffic logging method of any of claims 4-7.

13. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions for causing a processor, when executed, to implement the traffic logging method according to any of claims 1-7.