WO2019134291A1

WO2019134291A1 - Method for recording call information between program interfaces, and electronic device

Info

Publication number: WO2019134291A1
Application number: PCT/CN2018/082354
Authority: WO
Inventors: 廖嘉东; 陈少杰; 张文明
Original assignee: 武汉斗鱼网络科技有限公司
Priority date: 2018-01-05
Filing date: 2018-04-09
Publication date: 2019-07-11
Also published as: CN108228165B; CN108228165A

Abstract

A method for recording call information between program interfaces, and an electronic device, for providing a recording method for unifying call information of each program interface. A pre-set hook class is registered in an application program project, a method preceding program interface execution and a method after program interface execution are coded in the class. The method comprises: before a program interface in an application program project is called by an upper-layer program interface, calling the method preceding program interface execution to extract, from header information of a first http request of the upper-layer program interface, call information transferred by the upper-layer program interface, generating first private call information, determining call information needing to be transferred to a lower-layer program interface and encapsulating same into header information of a second http request (S101); and after the execution of the program interface, calling the method after program interface execution, generating second private call information of the program interface, splicing call information needing to be recorded and recording, to a log file, the call information needing to be recorded (S102).

Description

Method and electronic device for recording information between program interface

Technical field

The present invention relates to the field of electronic technologies, and in particular, to a method, an electronic device, and a readable storage medium for recording information between program interfaces.

Background technique

During the application development process, you may need to understand the calling process of the business layer and the service layer program interface, and obtain the calling information of the interface, such as: interface request source, interface address, interface execution time, and so on. In the prior art, interface call information is recorded in such a manner that code for recording call information is embedded in each interface to be recorded. The main drawback of this method is that each interface must be added with a record code, which is inefficient. At the same time, the record codes added by each interface are difficult to be unified, so that the recorded call information is inconsistent.

Summary of the invention

Embodiments of the present invention provide a method, an electronic device, and a readable storage medium for recording information between program interface interfaces, which are used to provide a call information for unifying each program interface without repeatedly adding a record code to a program interface. The logging method keeps the recorded call log information consistent.

In a first aspect, the present invention provides a method for recording information between program interface interfaces, wherein a preset hook class is registered in an application program, and the preset hook class is programmed with a pre-execution method and a program interface execution method. The method includes:

Before the program interface in the application project is called by the upper program interface, calling the program interface pre-execution method, and executing the pre-method from the header information of the first http request of the upper-level program interface by using the program interface Extracting the call information passed by the upper program interface, generating the first private call information of the program interface, determining the call information that needs to be passed to the lower program interface, and encapsulating the call information that needs to be passed to the lower program interface to the second http request Header information;

After the program interface is executed, the program interface is executed, and the method is executed by the program interface, and the second private call information of the program interface is generated, based on the call information and the information transmitted by the upper program interface. Decoding the first private information and the second private information, splicing out the call information that needs to be recorded, and recording the call information that needs to be recorded to the log file.

Optionally, the method of the pre-execution of the program interface includes: a method for setting an identifier of a program interface call, where the generating the first private call information of the program interface includes:

And generating, by the method for setting an identifier of the program interface, a first identifier of the program interface call, where the first private call information includes the first identifier.

Optionally, the calling information that is transmitted by the upper-level program interface includes any one or more combinations of the identifier of the application item, the link identifier of the calling request, and the identifier of the upper-level program interface, where the The call information of the lower level program interface includes any one or more combinations of the identifier of the application item, the link identifier of the call request, and the first identifier.

Optionally, the method for executing the pre-execution of the program interface includes: acquiring a time when the program interface starts to be executed, where the generating the first private call information of the program interface includes:

And acquiring, by the method for acquiring a time when the program interface starts execution, a start time at which the program interface starts to be executed, where the first private call information includes the start time.

Optionally, the method after the execution of the program interface includes a method for acquiring a time when the program interface ends execution, where the generating the second private call information of the program interface includes:

Obtaining, by the method for obtaining the time of execution of the program interface, an end time of ending execution of the program interface, where the second private call information includes the end time.

Optionally, the splicing out the call information that needs to be recorded, including:

Determining a call duration of the program interface based on the start time and the end time, and the call information to be recorded includes the call information.

Optionally, the call information to be recorded includes an identifier of the application item, a link identifier of the call request, an identifier of the upper program interface, the call duration, and the first identifier or A variety of combinations.

In a second aspect, an embodiment of the present invention provides an electronic device, where a preset hook class is registered in an application item in the electronic device, and a method before the execution of the program interface and a method after the program interface are written in the preset hook class The electronic device includes:

a first calling unit, configured to call the program interface pre-execution method before the program interface in the application project is called by the upper-level program interface, and execute the pre-method from the first program interface by using the program interface The call information transmitted by the upper program interface is extracted from the header information of the http request, the first private call information of the program interface is generated, the call information that needs to be passed to the lower program interface is determined, and the call needs to be transmitted to the lower program interface. Encapsulating information to the header information of the second http request;

a second calling unit, configured to: after the program interface is executed, invoke the program interface execution method, and execute a post-method by the program interface to generate second private call information of the program interface, based on the upper program The calling information delivered by the interface, the first private information and the second private information are spliced together with call information to be recorded, and the call information required to be recorded is recorded to a log file.

Optionally, the method in the pre-execution of the program interface includes a method for setting an identifier of a program interface call, where the first calling unit is used to:

Optionally, the calling information delivered by the upper-level program interface includes any one or more combinations of the identifier of the application item, the link identifier of the calling request, and the identifier of the upper-level program interface, where the need to be transmitted to The call information of the lower level program interface includes any one or more combinations of the identifier of the application item, the link identifier of the call request, and the first identifier.

Optionally, the method in the pre-execution of the program interface includes a method for acquiring a time when the program interface starts to be executed, where the first calling unit is used to:

Optionally, the method after the execution of the program interface includes a method for acquiring a time at which the program interface ends execution, and the second calling unit is configured to:

Optionally, the second calling unit is used to:

In a third aspect, an embodiment of the present invention provides an electronic device, where the electronic device includes a processor, and the processor is configured to implement a recording program interface as described in the foregoing first embodiment when executing a computer program stored in a memory. The steps of the method of invoking information.

In a fourth aspect, an embodiment of the present invention provides a readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the inter-programme interface call is implemented as described in the foregoing first embodiment. The steps of the method of information.

The above one or more technical solutions in the embodiments of the present application have at least one or more of the following technical effects:

In the technical solution of the embodiment of the present invention, when the application is developed, the preset hook class is registered in the application project, and the pre-execution method and the program interface execution method are written in the preset hook class; Before being called by the upper-level program interface, calling the pre-execution method of the program interface, extracting the call information transmitted by the upper-level program interface from the header information of the first http request of the upper-level program interface, generating the first private call information of the program interface, determining that the transfer is required Calling information to the lower level program interface; after the program interface is executed, calling the program interface to execute the method, generating the second private calling information of the program interface, based on the calling information, the first private information and the second private information transmitted by the upper program interface, The call information to be recorded is spliced; the call information to be recorded is recorded to the log file, and the call information that needs to be passed to the lower program interface is encapsulated to the header information of the second http request. Since there is no need to embed code that records the call information in each program interface, you only need to register a hook class in the program framework to perform specific operations before and after the program interface is executed. In this way, the cumbersome operation of embedding the code in each program interface is omitted, and the call information recording method of each program interface is unified, so that the recorded log information is kept consistent, so the efficiency is greatly improved, and it is advantageous. Unified management of the code base.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1 is a flowchart of a method for recording information between program interface interfaces in the first embodiment of the present invention;

2 is a schematic diagram of an electronic device in a second embodiment of the present invention;

3 is a schematic diagram of an electronic device in a third embodiment of the present invention.

Detailed ways

Embodiments of the present invention provide a method, an electronic device, and a readable storage medium for recording information between program interface interfaces, which are used to provide a call information for unifying each program interface without repeatedly adding a record code to a program interface. The logging method keeps the recorded call log information consistent. The preset hook class is registered in the application project, and the pre-execution method and the program interface post-execution method are written in the preset hook class, and the method includes: the program interface in the application project is called by the upper program interface Executing the pre-execution method of the program interface, and extracting, by using the pre-execution method of the program interface, the call information transmitted by the upper-level program interface from the header information of the first http request of the upper-level program interface, and generating the program interface The first private call information determines the call information that needs to be delivered to the lower-level program interface, and encapsulates the call information that needs to be delivered to the lower-level program interface to the header information of the second http request; after the execution of the program interface, the call site a method of executing a program interface, executing a post-method by the program interface, generating a second private call information of the program interface, based on the call information, the first private information, and the second Private information, splicing out the call information to be recorded, and recording the call information to be recorded to the date Zhi file.

The technical solutions of the present invention are described in detail below with reference to the accompanying drawings and specific embodiments. It is understood that the specific features of the embodiments and the embodiments of the present application are the detailed description of the technical solutions of the present application, and are not limited to the technical solutions of the present application. In the case of no conflict, the technical features in the embodiments of the present application and the embodiments may be combined with each other.

The term "and/or" in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

Example

Referring to FIG. 1 , a first embodiment of the present invention provides a method for recording call information between program interfaces. A preset hook class is registered in an application program, and a method and a program interface are executed before a program interface is written in a preset hook class. The method comprises the following steps:

S101: before the program interface in the application project is called by the upper program interface, calling the pre-execution method of the program interface, and executing, by the program interface, a header of the first http request from the upper-level program interface Extracting the call information passed by the upper program interface, generating the first private call information of the program interface, determining the call information that needs to be passed to the lower program interface, and packaging the call information that needs to be passed to the lower program interface to the second Header information of the http request;

S102: After the program interface is executed, calling the program interface execution method, and executing the post method by the program interface, generating second private call information of the program interface, and using the call information transmitted by the upper program interface The first private information and the second private information are spliced together with call information that needs to be recorded, and the call information that needs to be recorded is recorded to a log file.

The method before the execution of the program interface includes a method for setting an identifier of a program interface call, and a method for acquiring a time when the program interface starts to be executed. The method for executing the program interface includes a method for acquiring a time when the program interface ends execution. And generating, by the method for setting an identifier of the program interface, the first identifier of the program interface call, and acquiring, by the method for acquiring a time when the program interface starts to execute, acquiring a start time of the execution of the program interface, by using the acquiring program The method of ending the execution of the interface acquires the end time at which the program interface ends execution. The first private call information includes the first identifier, the start time, and the second private call information includes the end time. Splicing out the call information to be recorded includes: determining a call duration of the program interface based on the start time and the end time.

Further, the call information delivered by the upper program interface includes any one or more combinations of the identifier of the application item, the link identifier of the call request, and the identifier of the upper program interface, and the call information that needs to be delivered to the lower program interface. And including any one or more combinations of the identifier of the application item, the link identifier of the call request, and the first identifier. The call information to be recorded includes an identifier of the application item, a link identifier of the call request, an identifier of the superior program interface, the call duration, and any one or more combinations of the first identifiers.

Specifically, in the embodiment, when the application development is performed, the interception hook in the framework is used to record the program interface call information. This embodiment mainly describes the PHP as a development framework. The hook class is registered in the application project. The hook class is written with the method before the execution of the program interface and the method after the program interface is executed. The hook class creation process is as follows:

First, create a hook method class

Whether in the PHP framework or in the Go framework, to implement the interceptor function first, you must first create a hook method class. Therefore, you first need to create a hook class in which to write the pre-execution method code and the post-execution method code. The hook method class is registered in the application project.

Then, through step S101, a call of the method before the execution of the program interface is performed.

In this embodiment, the pre-execution of the program interface is called before each program interface is executed, and is configured to receive the header information of the first http request sent by the upper-level program interface, and initialize the program interface call information.

In the hook class created above, create a new public class, which includes the start method, and write the code before the execution of the program interface in start. The writing steps include the following steps:

a) receiving the header information of the first http request from the upper-level program interface

The header information of the first http request is obtained through the global variable $_SERVER in PHP, and the information required for the link record is read in the header: the identifier id of the application item, the link identifier id of the calling request, and the identifier id of the upper program interface. Wait for the call information passed by the superior program interface.

b) set the unique id of the program interface call

The unique identifier id (ie, the first identifier) of the program interface call is generated by the uniqid() function of PHP, and the uniqid function can randomly generate a unique id according to the current time.

c) Request http header information setting

Call PHP's curl_setopt method, the second parameter is filled with CURLOPT_POSTFIELDS, the third parameter is filled in the json string to set the header, the requested link identifier id, the application id of the application project, and b) generated in the step The first identifier is passed to the lower level program interface in the header information header of the second http request.

d) method of obtaining the time at which the program interface starts executing

Call the time() method of PHP to get the start time startTime of the program interface.

Then, through step S102, a call of the method after the execution of the program interface is performed.

Through the execution of the pre-method of the above program interface, the reception of the first http request header information header transmitted from the upper-level program interface has been completed, and the unique identifier id of the program interface call is initialized. After calling the program interface to execute the method, log the call information. In the hook class created in the above, create a new public class, including the end method in the class, and execute the method code after executing the program interface in the end. , the writing steps are as follows:

a) Calculate the program interface execution time

Call the time() method in PHP again to get the endTime end of the program interface execution, and use the endTime minus the start time startTime to get the program interface call duration value.

b) stitching out the call information to be recorded

The identifier id of the application item acquired by the foregoing method before the execution of the program interface, the link identifier id of the calling request, the identifier id of the upper-level program interface, the unique identifier id of the program interface call, and the method obtained by executing the method after the program interface Call the time value, the application name name is stored in the array, and the array is converted to a json string using the json_encode function.

c) record the call information to the log file

Use the date ("Ymd") function to get the date of the day, use the fopen function to generate or open the log file of the day's date, the second parameter of the fopen function fills in a+, and then use the fwrite function to write the string spliced in b) into the log file. The first parameter of fwrite is filled in the log file handle, and the second parameter is filled in the json string.

Through the above steps, the call of the hook class method is completed. So in the framework, you only need to register the hook class to record the link information.

Specifically, registering the hook method may include the following steps:

1) Create a hook.php file for centralized management of hook registration.

2) Use the $hook['pre_controller'] in the framework to register the start method before the controller executes. Assign an array to $hook['pre_controller']. The value of the class in the array is the name of the hook class created in this case, the value of function is start, the filename is the file name of the method of the hook class, and the filepath is the file path where the class method is located.

3) Use the $hook['post_controller'] in the framework to register the start method before the controller executes. Assign an array to $hook['post_controller']. The values in the array are the same as those in the previous 2) except that the function value is end.

Through the above process of creating a hook method in the framework and registering, a method method for recording the call information of the program interface is realized, and the method does not need to embed the code in each program interface, but can record information of all the program interfaces in the framework. The efficiency is very high. At the same time, the method eliminates the tedious labor of repeatedly writing the code of the previous call information, and makes the code uniform and easy to manage.

Further, the registered hook information may be used to retrieve the header information of the first http request before the execution of the program interface, including: calling the requested link identifier id (identifying the unique id of each request call chain), and identifying the identifier of the application item. The id, the identifier of the superior program interface, and other information, and generate information such as the unique id called by the program interface, the start time of the program interface call, and the like. Then, the information such as the link identifier id of the calling request, the identifier id of the application item, and the unique id called by the program interface are put into the header information of the second http request, and then passed to the next interface. After the program interface is executed, the call information such as the program interface call time is saved in the form of a log.

The method in this embodiment does not need to embed the code for recording the call information in the interface, and only needs to add a hook in the program framework to perform a specific operation before and after the execution of the program interface. This eliminates the cumbersome operation of embedding code in each program interface, and unifies the call information recording method of each program interface, so that the recorded log information remains consistent. Therefore, using this method greatly improves the efficiency and facilitates the unified management of the code base.

Referring to FIG. 2, a second embodiment of the present invention provides an electronic device, where a preset hook class is registered in an application item in the electronic device, and the pre-execution method is programmed in the preset hook class. After the program interface executes the method, the electronic device includes:

a first calling unit 201, configured to call the program interface pre-execution method before the program interface in the application project is called by the upper-level program interface, and execute the pre-method from the upper-level program interface by using the program interface Extracting the call information passed by the upper program interface from the header information of the http request, generating the first private call information of the program interface, determining the call information that needs to be passed to the lower program interface, and transmitting the need to the lower program interface. Invoking information encapsulated to the header information of the second http request;

a second calling unit 202, configured to: after the program interface is executed, invoke the program interface execution method, and execute a post-method by the program interface to generate second private call information of the program interface, based on the superior The call information transmitted by the program interface, the first private information and the second private information are spliced together with call information to be recorded, and the call information required to be recorded is recorded to a log file.

Specifically, in this embodiment, the electronic device is installed with a software development platform, and when the software development platform is used for application development, the interceptor hook in the framework is used to record the program interface call information.

This embodiment mainly describes the PHP as a development framework. Specifically, the hook class is registered in the application project, and the hook method is programmed with a pre-execution method and a post-execution method. The hook class creation process is as follows:

First, create a hook method class

Whether in the PHP framework or in the Go framework, to implement the interceptor function first, you must first create a hook method class. Therefore, you first need to create a hook class in which to write the pre-execution method code and the post-execution method code.

Then, write the method before the program interface is executed.

In this embodiment, by the first calling unit 201, the pre-execution of the program interface is called before each program interface is executed, and is used to receive the header information of the first http request sent by the upper-level program interface, and initialize the program. Interface call information.

b) set the unique id of the program interface call

c) Request http header information setting

d) method of obtaining the time at which the program interface starts executing

Then, the method is written after the execution of the program interface.

Through the execution of the pre-method of the above program interface, the reception of the first http request header information header transmitted from the upper-level program interface has been completed, and the unique identifier id of the program interface call is initialized. Further, the second calling unit 202 calls the program interface to execute the post method, and records the call information. In the hook class created in the foregoing, a new public class is created, and the end method is included in the class. After the program interface is executed, the method code is written. The writing steps are as follows:

a) Calculate the program interface execution time

b) stitching out the call information to be recorded

c) record the call information to the log file

Through the above steps, the writing of the hook class method is completed. So in the framework, you only need to register the hook class to record the link information.

Specifically, registering the hook method may include the following steps:

1) Create a hook.php file for centralized management of hook registration.

Further, the registered hook information may be used to retrieve the header information of the first http request before the execution of the program interface, including: calling the requested link identifier id (identifying the unique id of each request call chain), and identifying the identifier of the application item. The id, the identifier of the superior program interface, and other information, and generate information such as the unique id called by the program interface, the start time of the program interface call, and the like. After the program interface is executed, the call information such as the program interface call time is saved in the form of a log, and then the link identifier id of the call request, the identifier id of the application item, and the unique id called by the program interface are put into the first The header information of the two http request is passed to the next interface.

The electronic device in this embodiment does not need to embed the code for recording the call information in the interface, and only needs to add a hook in the program frame to perform a specific operation before and after the execution of the program interface. This eliminates the cumbersome operation of embedding code in each program interface, and unifies the call information recording method of each program interface, so that the recorded log information remains consistent. Therefore, the efficiency is greatly improved, and the unified management of the code base is facilitated.

Referring to FIG. 3, a third embodiment of the present invention provides an electronic device, where the electronic device includes: a processor 301, a memory 302, and is stored in the memory and operable on the processor. A computer program, for example, a program corresponding to a method of recording information between program interface interfaces in the first embodiment. The steps in the path detection in the first embodiment described above are implemented when the processor executes the computer program. Alternatively, the processor implements the functions of the modules/units in the electronic device of the second embodiment described above when the computer program is executed.

Illustratively, the computer program can be partitioned into one or more modules/units that are stored in the memory and executed by the processor to perform the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing a particular function, the instruction segments being used to describe the execution of the computer program in the computer device. For example, the computer program may be divided into functions of a first calling unit and a second calling unit, and a preset hook class is registered in an application item in the electronic device, and a program interface is executed in the preset hook class. Before the method and program interface are executed, the specific functions of each unit are as follows:

a second calling unit, configured to: after the program interface is executed, invoke the program interface execution method, and execute a post-method by the program interface to generate second private call information of the program interface, based on the upper-level program The calling information delivered by the interface, the first private information and the second private information are spliced together with call information to be recorded, and the call information required to be recorded is recorded to a log file.

The electronic device can include, but is not limited to, a processor, a memory. It will be understood by those skilled in the art that the schematic diagram 3 is merely an example of a computer device and does not constitute a limitation on an electronic device, and may include more or less components than those illustrated, or may combine certain components or different components. For example, the electronic device may further include an input and output device, a network access device, a bus, and the like.

The processor 301 may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like, which is the control center of the computer device, which is connected to various parts of the entire computer device using various interfaces and lines.

The memory 302 can be used to store the computer program and/or module, the processor implementing the method by running or executing a computer program and/or module stored in the memory, and invoking data stored in the memory Various functions of a computer device. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored. Data created according to the use of the mobile phone (such as audio data, video data, etc.). In addition, the memory may include a high-speed random access memory, and may also include non-volatile memory such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), and a Secure Digital (SD) card. , Flash Card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

Further, the processor 301 included in the electronic device further has the following functions:

The method of the program interface includes a method for setting an identifier of a program interface call, and the method for setting an identifier of the program interface is used to generate a first identifier that is invoked by the program interface, where the first private call information includes the First identification.

Further, the calling information delivered by the upper-level program interface includes any one or more combinations of the identifier of the application item, the link identifier of the calling request, and the identifier of the upper-level program interface, and the need to be transmitted to the lower-level program. The call information of the interface includes any one or more combinations of the identifier of the application item, the link identifier of the call request, and the first identifier.

The method of the pre-execution of the program interface includes: acquiring a time when the program interface starts to be executed, and acquiring, by the method for acquiring a time when the program interface starts execution, the start time of the execution of the program interface, where the first private call information includes The starting moment.

The method after the execution of the program interface includes a method for acquiring a time at which the program interface ends execution, and acquiring, by the method for obtaining a time at which the program interface ends execution, an end time at which the program interface ends execution, where the second private call information includes The end time.

Further, the call information to be recorded includes an identifier of the application item, a link identifier of the call request, an identifier of the upper program interface, the call duration, and the first identifier. combination.

A fourth embodiment of the present invention provides a computer readable storage medium having stored thereon a computer program, and the functional unit integrated by the electronic device in the second embodiment of the present invention is implemented in the form of a software functional unit and is independent When the product is sold or used, it can be stored in a computer readable storage medium. Based on such understanding, the present invention implements all or part of the flow of the method for invoking information between the recording program interfaces of the first embodiment, and may also be completed by a computer program to instruct related hardware, and the computer program may be stored in In a computer readable storage medium, the computer program, when executed by a processor, implements the steps of the various method embodiments described above. Wherein, the computer program comprises computer program code, which may be in the form of source code, object code form, executable file or some intermediate form. The computer readable medium may include any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-0nly Memory). , random access memory (RAM, Random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. It should be noted that the content contained in the computer readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in a jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, computer readable media Does not include electrical carrier signals and telecommunication signals.

In the technical solution of the embodiment of the present invention, when the application is developed, the preset hook class is registered in the application project, and the pre-execution method and the program interface execution method are written in the preset hook class; Before being called by the upper-level program interface, calling the pre-execution method of the program interface, extracting the call information transmitted by the upper-level program interface from the header information of the first http request of the upper-level program interface, generating the first private call information of the program interface, determining that the transfer is required Calling information to the lower level program interface; after the program interface is executed, calling the program interface to execute the method, generating the second private calling information of the program interface, based on the calling information, the first private information and the second private information transmitted by the upper program interface, The call information to be recorded is spliced; the call information to be recorded is recorded to the log file, and the call information that needs to be passed to the lower program interface is encapsulated to the header information of the second http request. Since there is no need to embed the code for calling the call information in each program interface, it is only necessary to register a hook class in the program framework to perform specific operations before and after the execution of the program interface. In this way, the cumbersome operation of embedding the code in each program interface is omitted, and the call information recording method of each program interface is unified, so that the recorded log information is kept consistent, so the efficiency is greatly improved, and it is advantageous. Unified management of the code base.

While the preferred embodiment of the invention has been described, it will be understood that Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the invention are within the scope of the invention

The invention is also intended to cover such modifications and variations within the scope of the equivalents.

Claims

A method for recording information between program interface interfaces, wherein a preset hook class is registered in an application item, and the preset hook class is programmed with a pre-execution method and a program interface post-execution method, and the method includes :

Before the program interface in the application project is called by the upper program interface, calling the program interface pre-execution method, and executing the pre-method from the header information of the first http request of the upper-level program interface by using the program interface Extracting the call information passed by the upper program interface, generating the first private call information of the program interface, determining the call information that needs to be passed to the lower program interface, and encapsulating the call information that needs to be passed to the lower program interface to the second http request Header information;

After the program interface is executed, the program interface is executed, and the method is executed by the program interface, and the second private call information of the program interface is generated, based on the call information and the information transmitted by the upper program interface. Decoding the first private information and the second private information, splicing out the call information that needs to be recorded, and recording the call information that needs to be recorded to the log file.
The method of claim 1, wherein the method of the pre-execution of the program includes a method of setting an identifier of a program interface call, and the generating the first private call information of the program interface includes:

And generating, by the method for setting an identifier of the program interface, a first identifier of the program interface call, where the first private call information includes the first identifier.
The method according to claim 2, wherein the call information transmitted by the upper program interface includes any one of an identifier of the application item, a link identifier of the call request, and an identifier of the upper program interface or In a plurality of combinations, the call information that needs to be delivered to the lower level program interface includes any one or more combinations of the identifier of the application item, the link identifier of the call request, and the first identifier.
The method of claim 3, wherein the method of executing the pre-execution of the program interface comprises: acquiring a time when the program interface starts to be executed, the generating the first private call information of the program interface, comprising:

And acquiring, by the method for acquiring a time when the program interface starts execution, a start time at which the program interface starts to be executed, where the first private call information includes the start time.
The method of claim 4, wherein the method of executing the program interface comprises: obtaining a method for ending the execution of the program interface, the generating the second private call information of the program interface, comprising:

Obtaining, by the method for obtaining the time of execution of the program interface, an end time of ending execution of the program interface, where the second private call information includes the end time.
The method according to claim 5, wherein said splicing out call information to be recorded comprises:

Determining a call duration of the program interface based on the start time and the end time, and the call information to be recorded includes the call information.
The method according to claim 6, wherein the call information to be recorded includes an identifier of the application item, a link identifier of the call request, an identifier of the upper program interface, the call duration, and a location Any one or more combinations of the first identifiers.
An electronic device, wherein a preset hook class is registered in an application item in the electronic device, wherein the preset hook class is programmed with a pre-execution method and a post-execution method, and the electronic device is include:

a first calling unit, configured to call the program interface pre-execution method before the program interface in the application project is called by the upper-level program interface, and execute the pre-method from the first program interface by using the program interface The call information transmitted by the upper program interface is extracted from the header information of the http request, the first private call information of the program interface is generated, the call information that needs to be passed to the lower program interface is determined, and the call needs to be transmitted to the lower program interface. Encapsulating information to the header information of the second http request;

a second calling unit, configured to: after the program interface is executed, invoke the program interface execution method, and execute a post-method by the program interface to generate second private call information of the program interface, based on the upper program The calling information delivered by the interface, the first private information and the second private information are spliced together with call information to be recorded, and the call information required to be recorded is recorded to a log file.
An electronic device, comprising: a processor, wherein the processor is configured to execute a call program information between the recording program interfaces according to any one of claims 1 to 7 when executing a computer program stored in a memory The steps of the method.
A readable storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the method of recording information between program interface interfaces according to any one of claims 1-7 step.