CN112685257A

CN112685257A - Interface log information processing method and device, storage medium and electronic equipment

Info

Publication number: CN112685257A
Application number: CN202011612657.5A
Authority: CN
Inventors: 黄一毅; 朱建立; 费亭
Original assignee: Ping An Securities Co Ltd
Current assignee: Ping An Securities Co Ltd
Priority date: 2020-12-30
Filing date: 2020-12-30
Publication date: 2021-04-20

Abstract

The scheme relates to a block chain technology, and provides a processing method, a device, a storage medium and electronic equipment of interface log information, which belong to the technical field of data processing, and the method comprises the following steps: if request information of a calling interface is received, parameter information contained in the request information is obtained; acquiring the calling state of the interface based on the calling feedback information of the interface, wherein the calling state is used for representing the calling result of the interface; and associating the calling state with the parameter information to obtain target log information. Wherein the target log information may be stored in the blockchain node. The method improves the readability of the interface log information and improves the processing efficiency of the interface log information.

Description

Interface log information processing method and device, storage medium and electronic equipment

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a method and an apparatus for processing interface log information, a computer-readable storage medium, and an electronic device.

Background

During the operation of the system or the application program, various interfaces are called, wherein the interfaces request a third party interface and are used as interface providers. Because the number of interfaces is large, log monitoring on the interface data is necessary for debugging the interface data, analyzing the data and optimizing the service. However, because the number of interfaces is large, and a large number of redundant codes exist in the generated log file, it is not easy to view and perform subsequent processing, so how to improve the readability of the information in the interface log file and further ensure the processing efficiency of the interface log file becomes a technical problem to be solved urgently.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

The embodiment of the disclosure provides a method and a device for processing interface log information, a computer-readable storage medium and an electronic device.

According to a first aspect of the present disclosure, there is provided a method for processing interface log information, including:

if request information of a calling interface is received, parameter information contained in the request information is obtained;

acquiring the calling state of the interface based on the calling feedback information of the interface, wherein the calling state is used for representing the calling result of the interface;

and associating the calling state with the parameter information to obtain target log information.

In an exemplary embodiment of the present disclosure, the call state includes call success and call exception;

the associating the calling state with the parameter information to obtain target log information includes:

if the calling state is calling abnormity, acquiring user behavior data which belongs to a preset time range when the request information is received;

simulating the operation behavior of the user according to the user behavior data and the parameter information and generating a simulation file;

and associating the simulation file, the parameter information and the calling state to obtain the target log information.

In an exemplary embodiment of the present disclosure, acquiring the parameter information included in the request information includes:

analyzing the request information;

identifying the parameter type corresponding to the parameter name contained in the request information according to a preset parameter name and parameter type mapping table;

and acquiring parameter information corresponding to each parameter name by adopting an acquisition strategy corresponding to the parameter type based on the parameter type of each parameter name.

In an exemplary embodiment of the present disclosure, if the parameter type is a privacy type, based on the parameter type of each parameter name, acquiring parameter information corresponding to each parameter name by using an acquisition policy corresponding to the parameter type, including:

encrypting the parameter information corresponding to the parameter name to obtain encrypted parameter information;

and replacing the parameter information corresponding to the parameter name with the encrypted parameter information.

In an exemplary embodiment of the present disclosure, if the parameter type is a special transmission type, based on the parameter type of each parameter name, acquiring parameter information corresponding to each parameter name by using an acquisition policy corresponding to the parameter type, including:

acquiring a transmission strategy corresponding to the parameter name based on the parameter name;

and aiming at the parameter information corresponding to the parameter name, adopting the transmission strategy to extract information so as to obtain target parameter information corresponding to the parameter information.

In an exemplary embodiment of the present disclosure, the method further includes:

acquiring the parameter type of the parameter information based on the parameter information;

based on the parameter type, obtaining annotation information corresponding to the parameter type;

and associating the annotation information with the parameter information and storing the annotation information and the parameter information in the target log information.

if a viewing request for the target log information is received, displaying a target log information list;

and displaying the specific content of the selected target log information according to the selected target log information in the target log information list.

According to a second aspect of the present disclosure, there is provided an interface log information processing apparatus, including:

the first acquisition module is used for acquiring parameter information contained in request information if the request information of a calling interface is received;

the second obtaining module is used for obtaining the calling state of the interface based on the calling feedback information of the interface, and the calling state is used for representing the calling result of the interface;

and the processing module is used for correlating the calling state with the parameter information to obtain target log information.

According to a third aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method of processing interface log information as in any one of the above.

According to a fourth aspect of the present disclosure, there is provided an electronic device comprising:

a processor; and

a memory having a computer program stored thereon;

wherein the processor is configured to implement the processing method of the interface log information according to any one of the above items via execution of the computer program.

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:

based on the embodiments of the present disclosure, if request information for calling an interface is received, parameter information included in the request information is acquired, and a calling state of the interface is acquired based on calling feedback information of the interface, where the calling state is used to indicate a calling result of the interface, and then the calling state and the parameter information are associated to obtain target log information, so that a process of calling the interface is recorded, and key information is stored to obtain the target log information, thereby reducing redundant codes in the log information, improving readability of the target log information, and further ensuring processing efficiency of an interface log file.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

Fig. 1 shows a schematic diagram of an exemplary system architecture to which the technical solution of the embodiments of the present application can be applied.

Fig. 2 shows a flow diagram of a processing method of interface log information according to an embodiment of the present application.

Fig. 3 shows a flowchart of step S230 in the processing method of the interface log information of fig. 2 according to an embodiment of the present application.

Fig. 4 is a schematic flowchart illustrating parameter information acquisition in a processing method of interface log information according to an embodiment of the present application.

Fig. 5 shows a flowchart of step S430 in the processing method of the interface log information of fig. 4 according to an embodiment of the present application.

Fig. 6 shows a flowchart of step S430 in the processing method of the interface log information of fig. 4 according to an embodiment of the present application.

Fig. 7 is a schematic flowchart illustrating obtaining annotation information further included in the processing method of interface log information according to an embodiment of the present application.

Fig. 8 is a schematic flowchart illustrating viewing of target log information further included in the interface log information processing method according to an embodiment of the present application.

Fig. 9 shows a schematic block diagram of the interface log information processing apparatus according to an embodiment of the present application.

FIG. 10 shows a schematic block diagram of an electronic device according to one embodiment of the present application.

FIG. 11 shows a schematic diagram of a computer-readable storage medium according to an embodiment of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

As shown in fig. 1, the system architecture may include a terminal device (e.g., one or more of a smartphone 101, a tablet computer 102, and a portable computer 103 shown in fig. 1, but may also be a desktop computer, etc.), a network 104, and a server 105. The network 104 serves as a medium for providing communication links between terminal devices and the server 105. Network 104 may include various connection types, such as wired communication links, wireless communication links, and so forth.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, server 105 may be a server cluster comprised of multiple servers, or the like.

A user may use a terminal device to interact with the server 105 over the network 104 to receive or transmit information or the like. The server 105 may be a server that provides various services. For example, when the user transmits request information for calling an interface by using the terminal device 103 (or the terminal device 101 or 102), the server 105 may obtain parameter information included in the request information when receiving the request information for calling the interface, and obtain a calling state of the interface based on calling feedback information of the interface, where the calling state is used to indicate a calling result of the interface, and then associate the calling state with the parameter information to obtain target log information.

It should be noted that the method for processing the interface log information provided in the embodiment of the present application is generally executed by the server 105, and accordingly, the processing device for the interface log information is generally disposed in the server 105. However, in other embodiments of the present application, the terminal device may also have a function similar to that of the server, so as to execute the scheme of the interface log information processing method provided in the embodiments of the present application.

The implementation details of the technical solution of the embodiment of the present application are set forth in detail below:

fig. 2 shows a flow diagram of a processing method of interface log information according to an embodiment of the present application. Referring to fig. 2, the processing method at least includes steps S210 to S230, which are described in detail as follows:

in step S210, if request information for invoking an interface is received, parameter information included in the request information is obtained.

The interface may be a program structure for exchanging information with the outside in a system or an application program, and may acquire the required information by calling the interface.

The request information for invoking the interface may be request information for accessing the interface, and the request information may include various parameter information required for invoking the interface, for example, the parameter information may include, but is not limited to, an interface name, a user name, a password, and time information, and the like.

In this embodiment, the server may parse the received request information for calling the interface, acquire various parameter information included in the request information, and record the acquired parameter information.

In step S220, based on the call feedback information of the interface, a call state of the interface is obtained, where the call state is used to indicate a call result of the interface.

The call feedback information may be information for feeding back a call result of the interface, and after the call of the interface is completed, the interface may send the call feedback information to the terminal or the server, so that the terminal or the server knows whether the call of the interface is successful.

The call state may be information used to indicate whether the interface is successfully called, and the call feedback information may include a call state of the interface to specify whether the interface is successfully called, for example, a call state of "1" indicates that the interface is successfully called, a call state of "0" indicates that the interface is failed to be called, or a call state of "a" indicates that the interface is successfully called, and a call state of "b" indicates that the interface is failed to be called, which is merely an illustrative example, and this application is not limited in this respect.

In this embodiment, the server or the terminal may intercept the call feedback information fed back by the interface, and analyze the call feedback information, so as to obtain a call state used for representing a call result of the interface from the call feedback information, and store the call state.

Specifically, a person skilled in the art may establish an information interceptor through AOP (Aspect Programming), and when request information and call feedback information of a call interface are generated, the information interceptor may intercept and acquire the request information and the call feedback information for subsequent processing.

In step S230, the calling status and the parameter information are associated to obtain target log information.

In this embodiment, after intercepting the call feedback information returned by the interface, that is, after indicating that the interface has completed the call, the call state and the parameter information may be associated to obtain the target log information. It can be clear that, since the target log information only includes the parameter information, the calling state and other key parameters and does not include various redundant codes, readability of the target log information can be improved, a technician can quickly determine technical problems encountered when calling the interface according to the target log information, and processing efficiency of the interface log file is improved.

It is emphasized that, in order to further ensure the privacy and security of the target log information, the target log information may also be stored in a node of a block chain.

Based on the embodiment shown in fig. 2, fig. 3 shows a flowchart of step S230 in the processing method of the interface log information of fig. 2 according to an embodiment of the present application. Referring to fig. 3, the calling status includes a calling success and a calling exception, and the step S230 at least includes steps S310 to S330, which are described in detail as follows:

in step S310, if the calling status is abnormal, user behavior data belonging to a predetermined time range when the request information is received is acquired.

The user behavior data may be information recording operations performed by the user on the terminal or the server, such as operations performed by the user on an interface or information input by the user.

The predetermined time range may be a time range preset by a person skilled in the art, for example, the predetermined time range may be 3 minutes, 5 minutes, or 7 minutes, and the like, and the above examples are only exemplary and are not limited herein.

In this embodiment, when the obtained calling state is calling exception, the user behavior data of the user belonging to the predetermined time range when the request information of the calling interface is received may be correspondingly obtained, for example, the time for receiving the request information is 16:00, and the predetermined time range is 5 minutes, and when the calling state is detected as calling exception, the user behavior data within the predetermined time range, that is, the user behavior data within 15:55 to 16:00, is correspondingly obtained.

In step S320, according to the user behavior data and the parameter information, an operation behavior of the user is simulated and a simulation file is generated.

The simulation file can be a file generated by simulating the operation behavior of the user, the simulation file can be a screen recording file or a screen capturing file, and the like, and the operation performed by the user before the interface is called can be intuitively known according to the simulation file, so that the subsequent analysis is facilitated.

In this embodiment, the operation of the user is simulated according to the acquired user behavior data and parameter information to generate a simulation file. Specifically, a user operation sequence can be correspondingly generated according to the user behavior data and the sequence of operations, the user operations are sequentially simulated according to the user operation sequence during simulation, and the user operations are called according to the parameter information during interface calling, so that the user operations before the interface calling can be known according to the simulation file, and the reason for the abnormal interface calling can be conveniently known during subsequent analysis.

In step S330, the simulation file, the parameter information, and the calling status are associated to obtain the target log information.

In this embodiment, according to the generated simulation file, the parameter information, and the call state are stored in association, so as to obtain target log information.

Therefore, when analyzing the reason of the interface calling abnormity, a technician can acquire the parameter information and the simulation file of the calling interface according to the target log information, can quickly know the basic condition of the calling interface, and is convenient for analyzing the reason of the interface calling abnormity.

Based on the embodiment shown in fig. 2, fig. 4 is a schematic flowchart illustrating a process of acquiring parameter information in a method for processing interface log information according to an embodiment of the present application. Referring to fig. 4, acquiring the parameter information included in the request information at least includes steps S410 to S430, which are described in detail as follows:

in step S410, the request information is parsed.

In this embodiment, the server or the terminal may parse the received request information for invoking the interface to obtain information included in the request information.

In step S420, a parameter type corresponding to the parameter name included in the request information is identified according to a preset parameter name and parameter type mapping table.

The parameter name and parameter type mapping table may be a list of parameter types corresponding to parameter information preset by a person skilled in the art and used for determining each parameter name, and the parameter name and parameter type mapping table includes each parameter name and a parameter type corresponding to each parameter name. For example, the parameter type of the parameter information corresponding to the parameter name "password" is a secret type, and so on.

In this embodiment, according to a preset parameter name and parameter type mapping table, the parameter name included in the parameter name and parameter type mapping table is compared with the parameter name included in the request information of the calling interface, and if the parameter name in the request information is the same as the parameter name included in the parameter name and parameter type mapping table, the parameter type of the parameter name is correspondingly obtained from the parameter name and parameter type mapping table.

In step S430, based on the parameter type of each parameter name, an obtaining policy corresponding to the parameter type is adopted to obtain parameter information corresponding to each parameter name.

The obtaining strategy may be a obtaining manner of obtaining parameter information corresponding to each parameter type, which is preset by a person skilled in the art. It should be understood that parameter information of different parameter types may correspond to different acquisition strategies, so that the parameter information is adaptively processed according to the parameter types.

In this embodiment, according to the parameter type corresponding to the determined parameter name, an acquisition policy corresponding to the parameter type is acquired from preset acquisition policies, and the parameter information corresponding to the parameter name is acquired by using the acquisition policy, so as to adaptively process the parameter information according to different parameter types.

Based on the embodiments shown in fig. 2 and fig. 4, fig. 5 shows a flowchart of step S430 in the processing method of the interface log information of fig. 4 according to an embodiment of the present application. Referring to fig. 5, if the parameter type is the security type, the step S430 at least includes steps S510 to S520, which are described in detail as follows:

in step S510, the parameter information corresponding to the parameter name is encrypted to obtain encrypted parameter information.

The security type may be a type that the parameter information needs to be secured, such as privacy information such as a user's password.

In this embodiment, when the parameter type corresponding to the parameter name is a security type, it indicates that the parameter information needs to be secured to prevent property loss of the user. Therefore, the parameter information can be encrypted to obtain encrypted parameter information, and the privacy information of the user is prevented from being leaked.

In an embodiment of the present application, a random code corresponding to the parameter information may be generated according to the parameter information, and the random code and the parameter information are associated, so that when a subsequent technician analyzes a reason for an abnormal interface call, the parameter information associated with the random code may be obtained according to the random code, and request information of a call interface may be restored according to the parameter information.

In step S520, the encrypted parameter information is substituted for the parameter information corresponding to the parameter name.

In the embodiment, when the parameter information acquired from the request information of the calling interface is recorded, the encrypted parameter information is substituted for the original parameter information corresponding to the parameter name, so that the privacy information of the user is prevented from being leaked, and the property safety of the user is protected.

Based on the embodiments shown in fig. 2 and fig. 4, fig. 6 shows a flowchart of step S430 in the processing method of the interface log information of fig. 4 according to an embodiment of the present application. Referring to fig. 6, if the parameter type is a special transmission type, step S430 at least includes step S610 to step S620, which are described in detail as follows:

in step S610, based on the parameter name, an extraction policy corresponding to the parameter name is acquired.

The special transmission type may be a parameter type that requires a special transmission mode to transmit information, for example, a transmission mode such as desensitizing parameter information and then transmitting the desensitized parameter information.

The extraction policy may be an extraction manner preset by those skilled in the art for extracting parameter information of a specific transmission type.

In this embodiment, a person skilled in the art may set a corresponding extraction policy in advance according to a transmission mode of the parameter information of the special transmission type, and obtain the extraction policy corresponding to the parameter name when it is determined that the parameter type corresponding to the parameter name is the special transmission type. It should be understood that different special transmission modes may correspond to different extraction strategies, for example, for desensitized parameter information, reverse processing needs to be performed on the parameter information to obtain parameter information before desensitization, or decryption needs to be performed on encrypted parameter information, and so on.

In step S620, for the parameter information corresponding to the parameter name, the extraction policy is used to perform information extraction processing, so as to obtain target parameter information corresponding to the parameter information.

In this embodiment, an extraction policy corresponding to a special transmission type is adopted for parameter information corresponding to the special transmission type, so as to extract target parameter information corresponding to the parameter information, where the target parameter information is real parameter information corresponding to the parameter information.

In the embodiment shown in fig. 6, the parameter information of the special transmission type is extracted and processed through the preset extraction strategy, so that the parameter information transmitted by adopting different special transmission modes can be adaptively extracted, the accuracy of parameter information extraction is ensured, a technician is not required to perform manual extraction, and the efficiency of the acquired parameter information is improved.

Based on the embodiment shown in fig. 2, fig. 7 is a schematic flowchart illustrating a process of obtaining annotation information further included in the interface log information processing method according to an embodiment of the present application. Referring to fig. 7, acquiring the annotation information at least includes steps S710 to S730, which are described in detail as follows:

in step S710, a parameter type of the parameter information is obtained based on the parameter information.

In this embodiment, based on the parameter information obtained from the request information, the parameter type of the parameter information may be determined according to the parameter name corresponding to the parameter information, for example, the parameter type of the password is a secret type, and the like. Specifically, a parameter name and parameter type correspondence table may be pre-established, the parameter name included in the correspondence table is compared with the parameter name of the parameter information acquired in the request information, and if the parameter name and the parameter name are consistent, the parameter type corresponding to the parameter name is acquired correspondingly, so as to obtain the parameter type of the parameter information.

In step S720, based on the parameter type, annotation information corresponding to the parameter type is acquired.

The annotation information may be, among other things, annotation content for explaining the meaning or role of the parameter information. According to the annotation information, a technician can quickly know the meaning and the function of the parameter information, and the technician can conveniently understand the parameter information.

In this embodiment, a person skilled in the art may pre-establish a corresponding relationship table between a parameter type and annotation information, where the corresponding relationship table includes a parameter type of parameter information to be added with annotation content and annotation content corresponding to the parameter type, and query the corresponding relationship table according to the parameter type of the parameter information, that is, obtain annotation information corresponding to the parameter information of the parameter type correspondingly.

In step S730, the annotation information is associated with the parameter information and stored in the target log information.

In the embodiment, the acquired annotation information and the corresponding parameter information are stored in an associated manner, that is, the annotation content is correspondingly added to the target log information and stored, so that a technician can quickly know the meaning and the effect of the parameter information when reading the target log information in the subsequent process, the reading efficiency of the technician on the target log information is improved, and the processing efficiency of the target log information is further improved.

Based on the embodiment shown in fig. 2, fig. 8 is a schematic flow chart illustrating viewing target log information further included in the interface log information processing method according to an embodiment of the present application. Referring to fig. 8, the viewing target log information at least includes steps S810 to S820, which are described in detail as follows:

in step S810, if a request for viewing the target log information is received, a target log information list is displayed.

Wherein the viewing request for the target log information may be information for requesting viewing of the target log information. In an example, when the technician needs to view the target log information, a specific area on the interface (e.g., a "view" button on the interface, etc.) can be clicked to generate and send a view request for the target log information.

The target log information list may be a list including target log information that is established historically. When the server or the terminal receives a viewing request for the target log information, the target log information list is displayed on an interface so that a technician can select specific target log information to view. In an example, the target log information in the target log information list may be arranged according to the sequence of the creation time of the target log information list, so that a technician can select the newly created target log information.

In step S820, the specific content of the selected target log information is displayed based on the target log information selected in the target log information list.

In this embodiment, a technician may select specific target log information in the target log information list for viewing through an input device (e.g., an input keyboard or a touch-sensitive display screen) configured by the server or the terminal, for example, the technician may click a specific target log information in the target log information list or input a serial number of a specific target log information, and so on. And after the server or the terminal determines the target log information selected by the technician in the target log information list, displaying the specific content of the target log information on the interface correspondingly for the technician to check.

In the embodiment shown in fig. 8, by establishing the target log information list, the technician can quickly check the specific content of the required target log information, and thus, the processing efficiency of the technician on the interface log information can be improved.

The disclosure also provides a device for processing the interface log information. Referring to fig. 9, the processing apparatus may include a first obtaining module 910, a second obtaining module 920, and a processing module 930. Wherein:

the first obtaining module 910 is configured to, if request information for calling an interface is received, obtain parameter information included in the request information;

the second obtaining module 920 is configured to obtain a calling state of the interface based on the calling feedback information of the interface, where the calling state is used to indicate a calling result of the interface;

the processing module 930 is configured to associate the call state with the parameter information to obtain target log information.

The specific details of each module in the device for processing interface log information have been described in detail in the method for processing corresponding interface log information, and therefore are not described herein again.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

An electronic device 500 according to this embodiment of the invention is described below with reference to fig. 10. The electronic device 500 shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 10, the electronic device 500 is embodied in the form of a general purpose computing device. The components of the electronic device 500 may include, but are not limited to: the at least one processing unit 510, the at least one memory unit 520, and a bus 530 that couples various system components including the memory unit 520 and the processing unit 510.

Wherein the storage unit stores program code that is executable by the processing unit 510 to cause the processing unit 510 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary methods" of the present specification. For example, the processing unit 510 may perform step 210 as shown in fig. 2: if request information of a calling interface is received, parameter information contained in the request information is obtained; step S220: acquiring the calling state of the interface based on the calling feedback information of the interface, wherein the calling state is used for representing the calling result of the interface; step S230, associating the calling status with the parameter information to obtain target log information.

The memory unit 520 may include a readable medium in the form of a volatile memory unit, such as a random access memory unit (RAM)5201 and/or a cache memory unit 5202, and may further include a read only memory unit (ROM) 5203.

Storage unit 520 may also include a program/utility 5204 having a set (at least one) of program modules 5205, such program modules 5205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 530 may be one or more of any of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 500 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 500, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 500 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 550. Also, the electronic device 500 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 560. As shown, the network adapter 560 communicates with the other modules of the electronic device 500 over the bus 530. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 500, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.

Further, the computer-readable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the blockchain node, and the like.

Referring to fig. 11, a program product 600 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, 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 portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

The block chain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A method for processing interface log information is characterized by comprising the following steps:

2. The method of claim 1, wherein the call state comprises call success and call exception;

3. The method of claim 1, wherein obtaining the parameter information included in the request information comprises:

analyzing the request information;

4. The method of claim 3, wherein if the parameter type is a privacy type, then based on the parameter type of each parameter name, adopting an obtaining policy corresponding to the parameter type to obtain the parameter information corresponding to each parameter name, comprising:

5. The method of claim 3, wherein if the parameter type is a special transmission type, then based on the parameter type of each parameter name, acquiring the parameter information corresponding to each parameter name by using an acquisition policy corresponding to the parameter type, comprising:

acquiring an extraction strategy corresponding to the parameter name based on the parameter name;

and aiming at the parameter information corresponding to the parameter name, adopting the extraction strategy to carry out information extraction processing so as to obtain target parameter information corresponding to the parameter information.

6. The method of claim 1, further comprising:

7. The method of claim 1, further comprising:

8. An apparatus for processing interface log information, comprising:

9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the method of processing interface log information according to any one of claims 1 to 7.

10. An electronic device, comprising:

a processor; and

a memory having a computer program stored thereon;

wherein the processor is configured to implement the processing method of the interface log information according to any one of claims 1 to 7 via execution of the computer program.