CN110990228A - Data interface monitoring method and device - Google Patents
Data interface monitoring method and device Download PDFInfo
- Publication number
- CN110990228A CN110990228A CN201911289578.2A CN201911289578A CN110990228A CN 110990228 A CN110990228 A CN 110990228A CN 201911289578 A CN201911289578 A CN 201911289578A CN 110990228 A CN110990228 A CN 110990228A
- Authority
- CN
- China
- Prior art keywords
- log
- data interface
- interface
- log information
- annotation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3068—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data format conversion
Abstract
The embodiment of the application provides a data interface monitoring method and a device, wherein the method comprises the following steps: establishing an association relation between a target data interface configured with a preset log annotation and a preset proxy object; carrying out log information acquisition on the target data interface through the proxy object, and persistently storing the acquired log information; according to the method and the system, the collection of the logs can be realized in a self-defined annotation mode on a system which does not invade the original system, the repeated output of log codes is reduced, meanwhile, the coupling between the log collection and the existing service system can be reduced, a large amount of repetitive work is reduced, and the work efficiency is improved.
Description
Technical Field
The present application relates to the field of data monitoring, and in particular, to a method and an apparatus for monitoring a data interface.
Background
With the increasing scale and complexity of modern computer systems, the number of running logs of the computer systems is increasing, but due to the huge scale and the disordered content of log data, a user has certain difficulty in viewing the log data, so that the computer systems have great significance in effectively collecting and processing the application running logs.
The inventor finds that log collection is realized by adding a log module in a service interface in the prior art, so that each interface needing log collection needs to be changed, namely, the original interfaces such as login, registration, order placement, payment, historical orders, balance inquiry, password modification and the like need to be changed and a log collection function is added, so that the workload is large and errors are easy to occur, and the method immerses the log collection function in service scenes such as registration, order placement, payment, historical orders, balance inquiry, password modification and the like, and is not beneficial to system upgrading and maintenance.
Disclosure of Invention
Aiming at the problems in the prior art, the application provides a data interface monitoring method and device, which can realize the collection of logs in a self-defined annotation mode on a system which does not invade the original system, reduce the repeated output of log codes, reduce the coupling between log collection and the existing service system, reduce a large amount of repetitive work and improve the working efficiency.
In order to solve at least one of the above problems, the present application provides the following technical solutions:
in a first aspect, the present application provides a data interface monitoring method, including:
establishing an association relation between a target data interface configured with a preset log annotation and a preset proxy object;
and carrying out log information acquisition on the target data interface through the proxy object, and persistently storing the acquired log information.
Further, the collecting log information of the target data interface by the proxy object includes:
acquiring corresponding pre-log information through the proxy object before the target data interface is executed, wherein the pre-log information comprises: at least one of an interface entry, an interface invocation person, and an interface start timestamp.
Further, the collecting log information of the target data interface by the proxy object further includes:
after the target data interface is executed, collecting corresponding post-log information through the proxy object, wherein the post-log information comprises: and the interface returns at least one of a value, interface time consumption and exception information.
Further, before the association relationship between the target data interface configured with the preset log annotation and the preset proxy object is established, the method further includes:
receiving an annotation self-defining instruction sent by a user and corresponding annotation information, and generating the log annotation.
In a second aspect, the present application provides a data interface monitoring apparatus, including:
the log annotation configuration module is used for establishing an association relation between the target data interface configured with the preset log annotation and a preset proxy object;
and the log information acquisition module is used for acquiring the log information of the target data interface through the proxy object and persistently storing the acquired log information.
Further, the log information collection module comprises:
a pre-log collection unit, configured to collect, by the proxy object, corresponding pre-log information before the target data interface is executed, where the pre-log information includes: at least one of an interface entry, an interface invocation person, and an interface start timestamp.
Further, the log information collection module further comprises:
a post-log collection unit, configured to collect, by the proxy object, corresponding post-log information after the target data interface is executed, where the post-log information includes: and the interface returns at least one of a value, interface time consumption and exception information.
Further, still include:
and the log annotation self-defining unit is used for receiving the annotation self-defining instruction sent by the user and the corresponding annotation information and generating the log annotation.
In a third aspect, the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the data interface monitoring method when executing the program.
In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the data interface monitoring method.
According to the technical scheme, the data interface monitoring method and the data interface monitoring device are characterized in that an association relation is established between a target data interface configured with preset log annotations and a preset proxy object; and the proxy object acquires the log information of the target data interface and persistently stores the acquired log information, so that the log can be managed in a centralized manner only by simple annotation configuration on the basis of not changing the service logic of the conventional system, the coupling of the conventional system and the log service logic is reduced, manual operation can be reduced, and the operation efficiency of enterprises is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flow chart of a data interface monitoring method in an embodiment of the present application;
FIG. 2 is a block diagram of a data interface monitoring apparatus according to an embodiment of the present application;
FIG. 3 is a second block diagram of a data interface monitoring apparatus according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In consideration of the fact that log acquisition is realized by adding a log module in a service interface in the prior art, each interface needing log acquisition needs to be changed, namely, the original log-in, registration, order placement, payment, historical order, balance inquiry, password modification and other interfaces need to be changed and log acquisition functions are added, so that the workload is large and errors are easy to occur; and the proxy object acquires the log information of the target data interface and persistently stores the acquired log information, so that the log can be managed in a centralized manner only by simple annotation configuration on the basis of not changing the service logic of the conventional system, the coupling of the conventional system and the log service logic is reduced, manual operation can be reduced, and the operation efficiency of enterprises is improved.
In order to realize the collection of logs by a self-defined annotation mode on a system which does not invade an original system, reduce the repeated output of log codes, reduce the coupling between log collection and the existing service system, reduce a large amount of repeated work and improve the working efficiency, the application provides an embodiment of a data interface monitoring method, and referring to fig. 1, the data interface monitoring method specifically comprises the following contents:
step S101: and establishing an association relation between the target data interface configured with the preset log annotation and the preset proxy object.
It is understood that the log annotation corresponds to a mark printed in the program, so that the program can perform corresponding log processing according to the log annotation.
Optionally, after the user-defined preset log annotation is configured in the target data interface, when the user calls the target data interface, a proxy object may be created for each target data interface configured with the log annotation.
It is understood that the definition of the proxy object is: a proxy is provided for other objects to control access to this object. In some cases, one object may not fit or directly reference another object, and the proxy object may act as an intermediary between the client and the target object. The proxy object will typically proxy the entire requester, and the client accesses the proxy object just as it would if accessing the requester, but it may do some extra work before or after the request, although the proxy object may eventually access the requester.
Step S102: and carrying out log information acquisition on the target data interface through the proxy object, and persistently storing the acquired log information.
It is understood that the collection and storage of log information is implemented in the proxy object, and one piece of log information is used when the target data interface is called once. The log typically contains the following information: the calling person of the interface, the parameter of the calling interface, the interface return result, the interface abnormal information, the interface time consumption and other information.
As can be seen from the above description, the data interface monitoring method provided in the embodiment of the present application can establish an association relationship between a target data interface configured with a preset log annotation and a preset proxy object; and the proxy object acquires the log information of the target data interface and persistently stores the acquired log information, so that the log can be managed in a centralized manner only by simple annotation configuration on the basis of not changing the service logic of the conventional system, the coupling of the conventional system and the log service logic is reduced, manual operation can be reduced, and the operation efficiency of enterprises is improved.
In order to accurately monitor the pre-set state of the target data interface before execution, in an embodiment of the data interface monitoring method of the present application, the following may be specifically included:
acquiring corresponding pre-log information through the proxy object before the target data interface is executed, wherein the pre-log information comprises: at least one of an interface entry, an interface invocation person, and an interface start timestamp.
In order to accurately monitor the post-state of the target data interface after the execution is completed, in an embodiment of the data interface monitoring method of the present application, the following may be specifically included:
after the target data interface is executed, collecting corresponding post-log information through the proxy object, wherein the post-log information comprises: and the interface returns at least one of a value, interface time consumption and exception information.
It can be understood that, firstly, the parameters of the log in the proxy object are obtained by obtaining the parameters of the interface (such as the amount of the order, the shipping address, the name of the contact person, the number of the mobile phone, etc.) before calling the proxied object (such as the order method), and recording the information of the registered account number of the application, the start timestamp (such as 57 minutes, 60 seconds, 256 milliseconds at 17 o 'clock of 29 o' clock of 2019) and the like of the user who calls the interface; secondly, acquiring a return result (such as { "code": 200, "msg": order placement success) and an end timestamp (such as 556 milliseconds of 57 minutes and 60 seconds at 17 points of 10 and 29 in 2019) of the interface while the method calls the proxied object to complete the business operation, and acquiring the interface time consumption (such as 556 and 256 ═ 400 milliseconds) by subtracting the end timestamp; finally, the abnormal information of the interface can be captured by calling the proxied object, the log information of the current piece is complete, and the log information is persisted into the database.
For example, in the user registration interface, log collection is implemented. The log annotation identifications that we just defined need to be configured on the user registration interface. When a user invokes a user registration interface, we generate a proxy object for the interface. The proxy object enables the interface to acquire the information of the interface caller before execution, and the interface enters the parameter (such as username: "zhangsan", password: "123456"), and the interface starts to call the parameter such as the timestamp. And executing the user registration interface of the proxy object after the user registration interface is executed, acquiring information such as an interface return result (such as { "code": 200, "msg": success "), an end timestamp and the like, if the user registration of the proxy object is abnormal, capturing abnormal information (such as {" code ": 3001 and password oversimplification) of the user, and finally storing a complete log in a database after the information in the log is acquired.
In order to improve the flexibility and pertinence of the log annotation, in an embodiment of the data interface monitoring method of the present application, the following may be further specifically included:
receiving an annotation self-defining instruction sent by a user and corresponding annotation information, and generating the log annotation.
It can be understood that firstly, the log annotation is created according to the annotation self-defining instruction sent by the user and the corresponding annotation information, and then, the self-defining log annotation is configured on the interface needing log collection.
Optionally, when the log is annotated by self-definition, marking of the interface is supported, for example, when a user calls the interface, the user returns exception information { code:500323, msg: "service timeout" } through url (×/order), and when the user views the log, the user can hardly know what the interface does. If tagged, e.g., (historical order interface,/order, { code:500323, msg: "service timeout" }), it is thus easy to locate what interface is in question.
In order to realize log collection by means of self-defined annotation without intruding into a system of an original system, reduce repeated output of log codes, reduce coupling between log collection and an existing service system, reduce a large amount of repetitive work, and improve work efficiency, the present application provides an embodiment of a data interface monitoring device for realizing all or part of contents of the data interface monitoring method, and referring to fig. 2, the data interface monitoring device specifically includes the following contents:
and the log annotation configuration module 10 is configured to establish an association relationship between the target data interface configured with the preset log annotation and the preset proxy object.
And the log information acquisition module 20 is configured to perform log information acquisition on the target data interface through the proxy object, and persistently store the acquired log information.
As can be seen from the above description, the data interface monitoring device provided in the embodiment of the present application can establish an association relationship between a target data interface configured with a preset log annotation and a preset proxy object; and the proxy object acquires the log information of the target data interface and persistently stores the acquired log information, so that the log can be managed in a centralized manner only by simple annotation configuration on the basis of not changing the service logic of the conventional system, the coupling of the conventional system and the log service logic is reduced, manual operation can be reduced, and the operation efficiency of enterprises is improved.
In order to accurately monitor the pre-state of the target data interface before execution and the post-state of the target data interface after execution is completed, in an embodiment of the data interface monitoring apparatus of the present application, referring to fig. 3, the log information collecting module 20 includes:
a pre-log collecting unit 21, configured to collect, by the proxy object, corresponding pre-log information before the target data interface is executed, where the pre-log information includes: at least one of an interface entry, an interface invocation person, and an interface start timestamp.
A post-log collecting unit 22, configured to collect, by the proxy object, corresponding post-log information after the target data interface is executed, where the post-log information includes: and the interface returns at least one of a value, interface time consumption and exception information.
In order to improve the flexibility and pertinence of the log annotation, in an embodiment of the data interface monitoring apparatus of the present application, the data interface monitoring apparatus further includes:
and the log annotation self-defining unit is used for receiving the annotation self-defining instruction sent by the user and the corresponding annotation information and generating the log annotation.
To further explain the present solution, the present application further provides a specific application example of the method for implementing data interface monitoring by using the data interface monitoring apparatus, which specifically includes the following contents:
step 1, creation of a custom log annotation.
And 2, configuring a custom log annotation on an interface needing log collection.
And 3, matching the interfaces needing log collection and generating proxy objects for the interfaces.
And 4, collecting log information in the proxy object, passing through message middleware, and persisting the log information into a unified database.
Optionally, when the log annotation is customized in step 1, marking the interface is supported. As an example, when a user calls an interface, we return exception information { code:500323, msg: "service timeout" } through url (×/order), and we have difficulty knowing what this interface does when looking at the log. If tagged, e.g., (historical order interface,/order, { code:500323, msg: "service timeout" }), we can easily locate what interface is in question,
meanwhile, step 1 also supports marking of the affiliated service, and for one example, in an order interface of a client, a series of upstream services such as a journey planning service, a billing service, an anti-cheating service, an automatic trip division journey and the like need to be called. Failure to invoke any of the above services may result in failure of the order interface. If we do not mark services, we can hardly decide what service is really a problem. The benefit of supporting the services to which they belong is to quickly locate problem services in the log.
Optionally, the log information is collected in the step 4, and the host name and the ip information of the corresponding response machine are collected while the log information is collected, so that the service which has a problem is conveniently positioned. And the third-party middleware with high writing performance is adopted, so that the accuracy of the effective log is ensured, the log is not lost, and the log error caused by concurrent writing of other logs is avoided. The log is collected in near real time, and the delay is controlled in the minute level. Because the data volume of the log is very large, the persistent data is supported to be horizontally expanded. Finally, different services can be centralized in the same database, and the use and analysis of data are facilitated.
As can be seen from the above description, the present application can also achieve at least the following technical effects:
on a system which does not invade the original system, the collection of the log is realized by a self-defined annotation mode, the repeated output of log codes is reduced, and the coupling of the log collection and the existing service system can be reduced. A large amount of repetitive work is reduced, and the working efficiency is improved.
In terms of hardware, in order to achieve log collection by means of customized annotation without intruding into a system of an original system, reduce repeated output of log codes, reduce coupling between log collection and an existing service system, reduce a large amount of repetitive work, and improve work efficiency, the present application provides an embodiment of an electronic device for implementing all or part of contents in the data interface monitoring method, where the electronic device specifically includes the following contents:
a processor (processor), a memory (memory), a communication Interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete mutual communication through the bus; the communication interface is used for realizing information transmission between the data interface monitoring device and relevant equipment such as a core service system, a user terminal, a relevant database and the like; the logic controller may be a desktop computer, a tablet computer, a mobile terminal, and the like, but the embodiment is not limited thereto. In this embodiment, the logic controller may be implemented with reference to the embodiment of the data interface monitoring method and the embodiment of the data interface monitoring apparatus in the embodiment, and the contents thereof are incorporated herein, and repeated descriptions are omitted.
It is understood that the user terminal may include a smart phone, a tablet electronic device, a network set-top box, a portable computer, a desktop computer, a Personal Digital Assistant (PDA), an in-vehicle device, a smart wearable device, and the like. Wherein, intelligence wearing equipment can include intelligent glasses, intelligent wrist-watch, intelligent bracelet etc..
In practical applications, part of the data interface monitoring method may be executed on the electronic device side as described above, or all operations may be completed in the client device. The selection may be specifically performed according to the processing capability of the client device, the limitation of the user usage scenario, and the like. This is not a limitation of the present application. The client device may further include a processor if all operations are performed in the client device.
The client device may have a communication module (i.e., a communication unit), and may be communicatively connected to a remote server to implement data transmission with the server. The server may include a server on the task scheduling center side, and in other implementation scenarios, the server may also include a server on an intermediate platform, for example, a server on a third-party server platform that is communicatively linked to the task scheduling center server. The server may include a single computer device, or may include a server cluster formed by a plurality of servers, or a server structure of a distributed apparatus.
Fig. 4 is a schematic block diagram of a system configuration of an electronic device 9600 according to an embodiment of the present application. As shown in fig. 4, the electronic device 9600 can include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this fig. 4 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.
In one embodiment, the data interface monitoring method function may be integrated into the central processor 9100. The central processor 9100 may be configured to control as follows:
step S101: and establishing an association relation between the target data interface configured with the preset log annotation and the preset proxy object.
Step S102: and carrying out log information acquisition on the target data interface through the proxy object, and persistently storing the acquired log information.
As can be seen from the above description, in the electronic device provided in the embodiment of the present application, an association relationship is established between a target data interface configured with a preset log annotation and a preset proxy object; and the proxy object acquires the log information of the target data interface and persistently stores the acquired log information, so that the log can be managed in a centralized manner only by simple annotation configuration on the basis of not changing the service logic of the conventional system, the coupling of the conventional system and the log service logic is reduced, manual operation can be reduced, and the operation efficiency of enterprises is improved.
In another embodiment, the data interface monitoring apparatus may be configured separately from the central processing unit 9100, for example, the data interface monitoring apparatus may be configured as a chip connected to the central processing unit 9100, and the data interface monitoring method function is realized by the control of the central processing unit.
As shown in fig. 4, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 also does not necessarily include all of the components shown in fig. 4; further, the electronic device 9600 may further include components not shown in fig. 4, which may be referred to in the art.
As shown in fig. 4, a central processor 9100, sometimes referred to as a controller or operational control, can include a microprocessor or other processor device and/or logic device, which central processor 9100 receives input and controls the operation of the various components of the electronic device 9600.
The memory 9140 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 9100 can execute the program stored in the memory 9140 to realize information storage or processing, or the like.
The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. Power supply 9170 is used to provide power to electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, an LCD display, but is not limited thereto.
The memory 9140 can be a solid state memory, e.g., Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 9140 could also be some other type of device. Memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 being used for storing application programs and function programs or for executing a flow of operations of the electronic device 9600 by the central processor 9100.
The memory 9140 can also include a data store 9143, the data store 9143 being used to store data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers for the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, contact book applications, etc.).
The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. The communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as in the case of a conventional mobile communication terminal.
Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby implementing ordinary telecommunications functions. The audio processor 9130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100, thereby enabling recording locally through the microphone 9132 and enabling locally stored sounds to be played through the speaker 9131.
An embodiment of the present application further provides a computer-readable storage medium capable of implementing all the steps in the data interface monitoring method with the execution subject being the server or the client in the foregoing embodiments, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program implements all the steps in the data interface monitoring method with the execution subject being the server or the client in the foregoing embodiments, for example, when the processor executes the computer program, the processor implements the following steps:
step S101: and establishing an association relation between the target data interface configured with the preset log annotation and the preset proxy object.
Step S102: and carrying out log information acquisition on the target data interface through the proxy object, and persistently storing the acquired log information.
As can be seen from the above description, in the computer-readable storage medium provided in the embodiment of the present application, an association relationship is established between a target data interface configured with a preset log annotation and a preset proxy object; and the proxy object acquires the log information of the target data interface and persistently stores the acquired log information, so that the log can be managed in a centralized manner only by simple annotation configuration on the basis of not changing the service logic of the conventional system, the coupling of the conventional system and the log service logic is reduced, manual operation can be reduced, and the operation efficiency of enterprises is improved.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A method for monitoring a data interface, the method comprising:
establishing an association relation between a target data interface configured with a preset log annotation and a preset proxy object;
and carrying out log information acquisition on the target data interface through the proxy object, and persistently storing the acquired log information.
2. The data interface monitoring method of claim 1, wherein the collecting log information of the target data interface by the agent object comprises:
acquiring corresponding pre-log information through the proxy object before the target data interface is executed, wherein the pre-log information comprises: at least one of an interface entry, an interface invocation person, and an interface start timestamp.
3. The data interface monitoring method of claim 1, wherein the collecting log information of the target data interface by the agent object further comprises:
after the target data interface is executed, collecting corresponding post-log information through the proxy object, wherein the post-log information comprises: and the interface returns at least one of a value, interface time consumption and exception information.
4. The data interface monitoring method according to claim 1, before the associating relationship between the target data interface configured with the preset log annotation and the preset proxy object is established, further comprising:
receiving an annotation self-defining instruction sent by a user and corresponding annotation information, and generating the log annotation.
5. A data interface monitoring device, comprising:
the log annotation configuration module is used for establishing an association relation between the target data interface configured with the preset log annotation and a preset proxy object;
and the log information acquisition module is used for acquiring the log information of the target data interface through the proxy object and persistently storing the acquired log information.
6. The data interface monitoring device of claim 5, wherein the log information collection module comprises:
a pre-log collection unit, configured to collect, by the proxy object, corresponding pre-log information before the target data interface is executed, where the pre-log information includes: at least one of an interface entry, an interface invocation person, and an interface start timestamp.
7. The data interface monitoring device of claim 5, wherein the log information collection module further comprises:
a post-log collection unit, configured to collect, by the proxy object, corresponding post-log information after the target data interface is executed, where the post-log information includes: and the interface returns at least one of a value, interface time consumption and exception information.
8. The data interface monitoring device of claim 5, further comprising:
and the log annotation self-defining unit is used for receiving the annotation self-defining instruction sent by the user and the corresponding annotation information and generating the log annotation.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the data interface monitoring method according to any one of claims 1 to 4 are implemented when the program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the data interface monitoring method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911289578.2A CN110990228A (en) | 2019-12-13 | 2019-12-13 | Data interface monitoring method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911289578.2A CN110990228A (en) | 2019-12-13 | 2019-12-13 | Data interface monitoring method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110990228A true CN110990228A (en) | 2020-04-10 |
Family
ID=70093862
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911289578.2A Pending CN110990228A (en) | 2019-12-13 | 2019-12-13 | Data interface monitoring method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110990228A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111881471A (en) * | 2020-07-21 | 2020-11-03 | 中国工商银行股份有限公司 | Non-intrusive log data desensitization method, device and system |
| CN112306803A (en) * | 2020-10-29 | 2021-02-02 | 金蝶云科技有限公司 | Performance monitoring method and related equipment |
| CN113268401A (en) * | 2021-06-16 | 2021-08-17 | 中移（杭州）信息技术有限公司 | Log information output method and device and computer readable storage medium |
| CN113762688A (en) * | 2021-01-06 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Business analysis system, method and storage medium |
| CN113778777A (en) * | 2020-06-28 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Log playback method and device |
| CN114911731A (en) * | 2022-03-16 | 2022-08-16 | 平湖市智周深鉴智能科技有限公司 | Method for designing modeled interface of complex system, electronic device and storage medium |
| CN115495718A (en) * | 2022-09-19 | 2022-12-20 | 广东云徙智能科技有限公司 | Method, device and equipment for authorizing back-end capability based on front-end declaration |
| CN116610532A (en) * | 2023-07-17 | 2023-08-18 | 山东浪潮数字商业科技有限公司 | Redis client monitoring method, system, electronic equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110290212A (en) * | 2019-06-28 | 2019-09-27 | 浙江大搜车软件技术有限公司 | Service call recording method, device, computer equipment and storage medium |
| US20190372829A1 (en) * | 2018-05-30 | 2019-12-05 | International Business Machines Corporation | Determining a storage network path utilizing log data |
-
2019
- 2019-12-13 CN CN201911289578.2A patent/CN110990228A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190372829A1 (en) * | 2018-05-30 | 2019-12-05 | International Business Machines Corporation | Determining a storage network path utilizing log data |
| CN110290212A (en) * | 2019-06-28 | 2019-09-27 | 浙江大搜车软件技术有限公司 | Service call recording method, device, computer equipment and storage medium |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113778777A (en) * | 2020-06-28 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Log playback method and device |
| CN111881471A (en) * | 2020-07-21 | 2020-11-03 | 中国工商银行股份有限公司 | Non-intrusive log data desensitization method, device and system |
| CN112306803A (en) * | 2020-10-29 | 2021-02-02 | 金蝶云科技有限公司 | Performance monitoring method and related equipment |
| CN113762688A (en) * | 2021-01-06 | 2021-12-07 | 北京沃东天骏信息技术有限公司 | Business analysis system, method and storage medium |
| CN113268401A (en) * | 2021-06-16 | 2021-08-17 | 中移（杭州）信息技术有限公司 | Log information output method and device and computer readable storage medium |
| CN113268401B (en) * | 2021-06-16 | 2022-10-04 | 中移（杭州）信息技术有限公司 | Log information output method and device and computer readable storage medium |
| CN114911731A (en) * | 2022-03-16 | 2022-08-16 | 平湖市智周深鉴智能科技有限公司 | Method for designing modeled interface of complex system, electronic device and storage medium |
| CN114911731B (en) * | 2022-03-16 | 2023-11-17 | 平湖市智周深鉴智能科技有限公司 | Modeling interface design method of complex system, electronic equipment and storage medium |
| CN115495718A (en) * | 2022-09-19 | 2022-12-20 | 广东云徙智能科技有限公司 | Method, device and equipment for authorizing back-end capability based on front-end declaration |
| CN115495718B (en) * | 2022-09-19 | 2023-10-13 | 广东云徙智能科技有限公司 | Front-end statement-based back-end capability authorization method, device and equipment |
| CN116610532A (en) * | 2023-07-17 | 2023-08-18 | 山东浪潮数字商业科技有限公司 | Redis client monitoring method, system, electronic equipment and storage medium |
| CN116610532B (en) * | 2023-07-17 | 2023-10-27 | 山东浪潮数字商业科技有限公司 | Redis client monitoring method, system, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110990228A (en) | Data interface monitoring method and device | |
| CN111031058A (en) | Websocket-based distributed server cluster interaction method and device | |
| CN112615753B (en) | Link abnormity tracking method, first node, second node and link | |
| CN110764881A (en) | Distributed system background retry method and device | |
| CN113435989A (en) | Financial data processing method and device | |
| CN107517188A (en) | A kind of data processing method and device based on Android system | |
| CN113485952A (en) | Data batch transmission method and device | |
| CN112689012A (en) | Cross-network proxy communication method and device | |
| CN111258902B (en) | Performance test method and performance test system based on SockJS server | |
| CN111767558A (en) | Data access monitoring method, device and system | |
| CN111324480A (en) | Large host transaction fault positioning system and method | |
| CN113791984B (en) | Automatic interface testing method and device | |
| CN113553152A (en) | Job scheduling method and device | |
| CN113434423A (en) | Interface test method and device | |
| CN111367592B (en) | Information processing method and device | |
| CN112559158A (en) | Micro-service timing task scheduling method and device | |
| CN111930624A (en) | Test link message data processing method and device | |
| CN112104787B (en) | Method and system for setting background of telephone interface | |
| CN111291254A (en) | Information processing method and device | |
| CN111818144B (en) | Message transmission method, device and system under remote service calling framework | |
| CN113760683B (en) | Log acquisition method and device | |
| CN113328911B (en) | Traffic link monitoring method and device during service operation | |
| CN113342501B (en) | System fault processing method and device | |
| CN111158744B (en) | Cross-platform heterogeneous data integration method and device | |
| CN115145554A (en) | Method and system for generating applet test preview code |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |