CN113448742A - Interface data acquisition method and device - Google Patents
Interface data acquisition method and device Download PDFInfo
- Publication number
- CN113448742A CN113448742A CN202010219851.0A CN202010219851A CN113448742A CN 113448742 A CN113448742 A CN 113448742A CN 202010219851 A CN202010219851 A CN 202010219851A CN 113448742 A CN113448742 A CN 113448742A
- Authority
- CN
- China
- Prior art keywords
- interface
- calling
- detector
- request
- configuration information
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 230000008569 process Effects 0.000 claims description 22
- 230000001360 synchronised effect Effects 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 10
- 230000000977 initiatory effect Effects 0.000 claims description 6
- 239000000523 sample Substances 0.000 claims description 5
- 238000013500 data storage Methods 0.000 claims description 3
- 238000012544 monitoring process Methods 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 10
- 238000001514 detection method Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000013480 data collection Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000009960 carding Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
- G06F9/548—Object oriented; Remote method invocation [RMI]
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses an interface data acquisition method and device, and relates to the technical field of computers. One embodiment of the method comprises: receiving an interface calling request, and determining a called interface; acquiring request entry parameters in the interface calling request by using a detector; and calling the interface, acquiring a return value after calling the interface by using the detector, and then transmitting the request entry parameter and the return value to a data monitoring center. In the complex calling chain among systems, the method and the system are convenient for the monitoring system to find problems in time by acquiring the entry parameter and the return value of the calling interface each time, so that the error cost is reduced.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an interface data acquisition method and device.
Background
The complexity of the existing service and system is continuously increased, the number of interfaces related to each system is continuously increased, and the problems of high maintenance cost, untimely updating, time consumption of all carding and even omission exist. In addition, if the system has problems, the related data of the interface needs to be on-line printed and debugged when being checked, and the problem reproduction and development are influenced.
The current approaches to the above problems mainly include:
1) in a complex micro-service architecture system, each front-end request forms a complex distributed service calling link, and an interface calling process is recorded for tracking and troubleshooting system problems;
2) the JSF (Java server Faces) interface services registered for each application are viewed through the platform.
In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:
1) invoking link tracing can only discover a service interface with a request, but cannot detect discovery for interfaces that have expired or have no request;
2) the platform can only inquire specific interface service, and other services such as http cannot be inquired;
3) the real scene of interface calling cannot be simulated, so that the problem is reproduced; and often the return value of the interface service is different due to different request access parameters;
4) currently, an interface data acquisition and detection functional component for application services is lacking.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for acquiring interface data, which can at least solve the problems of the prior art that interface data acquisition is not easy and a general acquisition tool is not available.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided an interface data acquisition method including: receiving an interface calling request, and determining a called interface; acquiring request entry parameters in the interface calling request by using a detector; and calling the interface, acquiring a return value after calling the interface by using the detector, and then transmitting the request entry parameter and the return value to a data monitoring center.
Optionally, before the receiving the interface call request, the method further includes: receiving an application starting instruction, and loading interface configuration information according to the application identifier in the application starting process; determining an interface corresponding to the interface configuration information by using the detector; wherein the interface is an application start registration interface.
Optionally, in the application starting process, before loading the interface configuration information according to the identifier of the application, the method further includes: instantiating single interface configuration information to obtain an interface configuration object; the interface configuration information comprises an interface configuration format; determining an interface which accords with the interface configuration format by using the detector so as to transmit the information of the interface configuration object and the determined interface to a storage unit; the determining, by the probe, an interface corresponding to the interface configuration information includes: and determining an interface by using the detector based on the interface information stored in the storage unit.
Optionally, the loading interface configuration information according to the identifier of the application includes: and judging whether a synchronous locking method for other threads to run exists at present, if not, running the synchronous locking method by using one thread to load interface configuration information corresponding to the identifier.
Optionally, the interfaces include an initiating registration interface and a non-initiating registration interface.
In order to achieve the above object, according to another aspect of the embodiments of the present invention, there is provided an interface data acquisition apparatus including:
the request receiving module is used for receiving an interface calling request and determining a called interface;
the detector is used for acquiring request input parameters in the interface calling request, calling the interface and acquiring a return value after calling the interface;
and the data storage engine is used for transmitting the request entry and the return value to a data monitoring center.
Optionally, the apparatus further includes an interface determining module, configured to: receiving an application starting instruction, and loading interface configuration information according to the application identifier in the application starting process; the detector is used for determining an interface corresponding to the interface configuration information; wherein the interface is an application start registration interface.
Optionally, the system further includes an information instantiation module, configured to: instantiating single interface configuration information to obtain an interface configuration object; the interface configuration information comprises an interface configuration format; determining an interface which accords with the interface configuration format by using the detector so as to transmit the information of the interface configuration object and the determined interface to a storage unit; the detector is used for: interface determination is performed based on the interface information stored in the storage unit.
Optionally, the detector is configured to: and judging whether a synchronous locking method for other threads to run exists at present, if not, running the synchronous locking method by using one thread to load interface configuration information corresponding to the identifier.
Optionally, the interfaces include an initiating registration interface and a non-initiating registration interface.
To achieve the above object, according to still another aspect of the embodiments of the present invention, an interface data acquisition electronic device is provided.
The electronic device of the embodiment of the invention comprises: one or more processors; a storage device, configured to store one or more programs, which when executed by the one or more processors, cause the one or more processors to implement any of the above-described interface data acquisition methods.
To achieve the above object, according to a further aspect of the embodiments of the present invention, there is provided a computer readable medium having a computer program stored thereon, the computer program, when executed by a processor, implementing any one of the above-mentioned interface data acquisition methods.
According to the scheme provided by the invention, one embodiment of the invention has the following advantages or beneficial effects: the method mainly solves the problem that how to obtain the entry parameter and the return value of each calling interface in a complex calling chain among systems is convenient for a monitoring system to find problems in time, so that the error cost is reduced, the whole implementation can be regarded as a middleware for interface calling detection and data collection, and the integrity and the universality are realized.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic main flow chart of an interface data acquisition method according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart diagram of an alternative interface data collection method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of the main modules of an interface data acquisition device according to an embodiment of the present invention;
FIG. 4 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
FIG. 5 is a schematic block diagram of a computer system suitable for use with a mobile device or server implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that the interfaces are of many kinds, including but not limited to HTTP interfaces and JSF interfaces, where the JSF interface needs to be registered when the application is started, and the HTTP interface does not need to be registered. Because most interfaces have one characteristic, the interfaces can be divided into two types, one type is the interface registered when the application is started, and the other type is the interface registered when the application is not started.
Referring to fig. 1, a main flowchart of an interface data acquisition method provided by an embodiment of the present invention is shown, including the following steps:
s101: receiving an interface calling request, and determining a called interface;
s102: acquiring request entry parameters in the interface calling request by using a detector;
s103: and calling the interface, acquiring a return value after calling the interface by using the detector, and then transmitting the request entry parameter and the return value to a data monitoring center.
In the above embodiment, as for steps S101 and S102, the present embodiment mainly monitors a call request to an interface. And under the premise of starting the application, data detection is carried out in the process of processing the interface calling request. And usually the interface called by the interface calling request is directly indicated; here, the interfaces are not limited to the application-initiated registration interface and the non-application-initiated registration interface.
The present invention performs service interception on a call request before calling an interface, for example, AOP (Aspect organized Programming) to capture a request entry in the request by using a probe, for example: http:// domain name/path? a value1& b value 2.
The AOP realizes the unified maintenance of the program function through a precompilation mode and a dynamic agent in the operation period, and can isolate all parts of the business logic by utilizing the AOP, so that the coupling degree between all parts of the business logic is reduced, the reusability of the program is improved, and the development efficiency is improved.
For step S303, the present invention also performs service interception before feeding back a return value after calling an interface, so as to capture the return value of the interface called this time, for example, various data structures, by using a detector, thereby completing the collection of interface data (including entry and return values).
Data collected by the detector can be transmitted to a data handling service in an active push or passive pull mode, and then the obtained data is pushed to a service monitoring center in real time through the data handling service so as to be used for operations such as unified interface monitoring, single-interface customized query, historical abnormal request reproduction and the like.
The data stored in the service monitoring center can be sequentially sequenced according to the calling time points of the corresponding interfaces, so that problem reproduction and tracking positioning can be timely performed when problems occur in application operation in the follow-up process.
Before and after the interface calling request is processed, the logic code of the detector is added to obtain the request entry in the calling request and the return value after the interface is called.
According to the method provided by the embodiment, the logic code of the detector is added to perform service interception before and after the interface call request is processed, the request entry parameter and the call return value are obtained, and the method is general in overall implementation and easy to operate; by collecting the interface data in real time, the centralized maintenance and the unified management of the interface data are facilitated, and a data basis is provided for the follow-up understanding of the system operation performance, the positioning of abnormal positions, the problem recurrence and the like.
Referring to fig. 2, a schematic flow chart of an alternative interface data acquisition method according to an embodiment of the present invention is shown, including the following steps:
s201: receiving an application starting instruction, loading interface configuration information according to the application identifier in the application starting process, and further determining an interface corresponding to the interface configuration information by using the detector; wherein, the interface is an application starting registration interface;
s202: receiving an interface calling request, and determining a called interface; the interface comprises a non-application starting registration interface besides an application starting registration interface;
s203: acquiring request entry parameters in the interface calling request by using a detector;
s204: and calling the interface, acquiring a return value after calling the interface by using the detector, and then transmitting the request entry parameter and the return value to a data monitoring center.
In the above embodiment, for the steps S202 to S204, reference may be made to the descriptions of the steps S101 to S103 shown in fig. 1, and details are not repeated here.
In the above embodiment, regarding step S201, the present embodiment is mainly directed to an interface that needs to be determined and registered in the application starting process, for example, a JSF interface.
After receiving a starting instruction of an application, firstly loading interface configuration information corresponding to the application; the configuration loading operation is performed when it is detected that the application starts to be started, and configuration files, configuration information, and the like included in each application are different, which may be specifically distinguished according to an identifier (for example, an application name and a number) thereof.
The application startup process is multi-threaded, and to ensure synchronous loading of interface configuration information by threads, a synchronized synchronization lock may be set for the threads, e.g.,
the Synchronized is a keyword of java language, and is used for locking an object, a method or a code block. When two concurrent threads access the locking synchronous code block in the same object, only one thread can be executed in the same time, and the other thread can be executed only after the current thread is executed. And to ensure that the detected interface configuration information is correct, thread safety needs to be ensured firstly.
For example, before running the method, thread a needs to check whether there are other threads B (or C, D, etc.) that are using the method, and if so, thread B (or C, D, etc.) runs this thread a after running the synchronized method; if not, the thread A is directly operated.
The loaded interface configuration information is then stored in a storage unit, such as an application context or JVM (Java Virtual Machine). It should be noted that most of the applications are started by using the spining management, but without spining, the configuration information may be stored in the JVM.
The interface configuration information in the storage unit may also be an instantiated ProviderConfig object. The ProviderConfig is a consumer configuration class, which contains interface registration/configuration information, and is convenient for information acquisition.
The information stored in the storage unit may also include interface information. Based on the configuration format in the interface configuration information, the probe determines all interfaces meeting the configuration format requirement. The configuration formats of different interfaces are different, similar to human fingerprints, and the interfaces can be used for identifying whether detection is needed or not.
And in the subsequent application starting process, the detector can extract the interfaces corresponding to the application in the storage unit according to the identification of the application. It should be noted that the probe is essentially a proxy service embedded in the application system, and has a negligible effect on the performance of the program running the application.
The method provided by the embodiment automatically detects the starting registration interface in the application starting process, realizes the quick query of the interface, avoids the complex interface debugging in the positioning problem and improves the research and development work efficiency.
According to the method provided by the embodiment of the invention, the whole detection process of the detector is divided into two steps, wherein the first step is to determine to start the registration interface in the application starting process, and the second step is to perform request participation and return value acquisition before and after processing the interface calling request after the application is started. The automatic detection of the service interface and the real-time collection of the interface data are integrally realized, so that the unified monitoring and problem reproduction of the unified interface are realized.
Referring to fig. 3, a schematic diagram of main modules of an interface data acquisition apparatus 300 according to an embodiment of the present invention is shown, including:
a request receiving module 301, configured to receive an interface call request and determine a called interface;
a detector 302, configured to collect a request entry in the interface invocation request, invoke the interface, and collect a return value after invoking the interface;
and the data storage engine 302 is used for transmitting the request entry and the return value to a data monitoring center.
The apparatus further includes an interface determining module 304 (not shown) for: receiving an application starting instruction, and loading interface configuration information according to the application identifier in the application starting process; the detector is used for determining an interface corresponding to the interface configuration information; wherein the interface is an application start registration interface.
The device for implementing the present invention further includes an information instantiation module 305 (not shown in the figure) for: instantiating single interface configuration information to obtain an interface configuration object; the interface configuration information comprises an interface configuration format; determining an interface which accords with the interface configuration format by using the detector so as to transmit the information of the interface configuration object and the determined interface to a storage unit; the detector 302 is configured to: interface determination is performed based on the interface information stored in the storage unit.
In the device for implementing the present invention, the detector 302 is configured to: and judging whether a synchronous locking method for other threads to run exists at present, if not, running the synchronous locking method by using one thread to load interface configuration information corresponding to the identifier.
In the implementation device of the invention, the interfaces comprise a starting registration interface and a non-starting registration interface.
In addition, the detailed implementation of the device in the embodiment of the present invention has been described in detail in the above method, so that the repeated description is not repeated here.
FIG. 4 illustrates an exemplary system architecture 400 to which embodiments of the invention may be applied.
As shown in fig. 4, the system architecture 400 may include terminal devices 401, 402, 403, a network 404, and a server 405 (by way of example only). The network 404 serves as a medium for providing communication links between the terminal devices 401, 402, 403 and the server 405. Network 404 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use terminal devices 401, 402, 403 to interact with a server 405 over a network 404 to receive or send messages or the like. Various communication client applications may be installed on the terminal devices 401, 402, 403.
The terminal devices 401, 402, 403 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 405 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 401, 402, 403.
It should be noted that the method provided by the embodiment of the present invention is generally executed by the server 405, and accordingly, the apparatus is generally disposed in the server 405.
It should be understood that the number of terminal devices, networks, and servers in fig. 4 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 5, shown is a block diagram of a computer system 500 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 5 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. 5, the computer system 500 includes a Central Processing Unit (CPU)501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the system 500 are also stored. The CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 501.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer 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 of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer 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. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer 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 computer readable signal medium may also be any computer readable medium that is not a computer 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 computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprises a request receiving module, a parameter acquisition module and a return value acquisition module. The names of these modules do not in some cases constitute a limitation on the module itself, and for example, the request receiving module may also be described as a "module that receives an interface call request".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise:
receiving an interface calling request, and determining a called interface;
acquiring request entry parameters in the interface calling request by using a detector;
and calling the interface, acquiring a return value after calling the interface by using the detector, and then transmitting the request entry parameter and the return value to a data monitoring center.
According to the technical scheme of the embodiment of the invention, the whole detection process of the detector is divided into two steps, wherein the first step is to determine to start the registration interface in the application starting process, and the second step is to perform request participation and return value acquisition before and after processing the interface calling request after the application is started. The automatic detection of the service interface and the real-time collection of the interface data are integrally realized, so that the unified monitoring and problem reproduction of the unified interface are realized.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. An interface data acquisition method, comprising:
receiving an interface calling request, and determining a called interface;
acquiring request entry parameters in the interface calling request by using a detector;
and calling the interface, acquiring a return value after calling the interface by using the detector, and then transmitting the request entry parameter and the return value to a data monitoring center.
2. The method of claim 1, prior to said receiving an interface call request, further comprising:
receiving an application starting instruction, and loading interface configuration information according to the application identifier in the application starting process;
determining an interface corresponding to the interface configuration information by using the detector; wherein the interface is an application start registration interface.
3. The method according to claim 2, wherein before loading interface configuration information according to the identifier of the application during the application starting process, the method further comprises:
instantiating single interface configuration information to obtain an interface configuration object; the interface configuration information comprises an interface configuration format;
determining an interface which accords with the interface configuration format by using the detector so as to transmit the information of the interface configuration object and the determined interface to a storage unit;
the determining, by the probe, an interface corresponding to the interface configuration information includes:
and determining an interface by using the detector based on the interface information stored in the storage unit.
4. The method according to claim 2 or 3, wherein the loading interface configuration information according to the identifier of the application comprises:
and judging whether a synchronous locking method for other threads to run exists at present, if not, running the synchronous locking method by using one thread to load interface configuration information corresponding to the identifier.
5. The method of claim 1, wherein the interfaces comprise an initiating registration interface and a non-initiating registration interface.
6. An interface data acquisition device, comprising:
the request receiving module is used for receiving an interface calling request and determining a called interface;
the detector is used for collecting the request entry parameters in the interface calling request; calling the interface, and collecting a return value after calling the interface;
and the data storage engine is used for transmitting the request entry and the return value to a data monitoring center.
7. The apparatus of claim 6, further comprising an interface determination module to: receiving an application starting instruction, and loading interface configuration information according to the application identifier in the application starting process;
the detector is used for determining an interface corresponding to the interface configuration information; wherein the interface is an application start registration interface.
8. The apparatus of claim 7, further comprising an information instantiation module to:
instantiating single interface configuration information to obtain an interface configuration object; the interface configuration information comprises an interface configuration format;
determining an interface which accords with the interface configuration format by using the detector so as to transmit the information of the interface configuration object and the determined interface to a storage unit;
the detector is used for: interface determination is performed based on the interface information stored in the storage unit.
9. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-5.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010219851.0A CN113448742B (en) | 2020-03-25 | 2020-03-25 | Interface data acquisition method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010219851.0A CN113448742B (en) | 2020-03-25 | 2020-03-25 | Interface data acquisition method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113448742A true CN113448742A (en) | 2021-09-28 |
| CN113448742B CN113448742B (en) | 2023-11-03 |
Family
ID=77806803
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010219851.0A Active CN113448742B (en) | 2020-03-25 | 2020-03-25 | Interface data acquisition method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113448742B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060010450A1 (en) * | 2004-07-08 | 2006-01-12 | Culter Bradley G | System and method for soft partitioning a computer system |
| CN101645032A (en) * | 2009-08-31 | 2010-02-10 | 金蝶软件（中国）有限公司 | Performance analysis method of application server and application server |
| CN104866383A (en) * | 2015-05-29 | 2015-08-26 | 北京金山安全软件有限公司 | Interface calling method and device and terminal |
| CN107888631A (en) * | 2016-09-28 | 2018-04-06 | 北京京东尚科信息技术有限公司 | A kind of interface interchange method and apparatus of configurable combination |
-
2020
- 2020-03-25 CN CN202010219851.0A patent/CN113448742B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060010450A1 (en) * | 2004-07-08 | 2006-01-12 | Culter Bradley G | System and method for soft partitioning a computer system |
| CN101645032A (en) * | 2009-08-31 | 2010-02-10 | 金蝶软件（中国）有限公司 | Performance analysis method of application server and application server |
| CN104866383A (en) * | 2015-05-29 | 2015-08-26 | 北京金山安全软件有限公司 | Interface calling method and device and terminal |
| CN107888631A (en) * | 2016-09-28 | 2018-04-06 | 北京京东尚科信息技术有限公司 | A kind of interface interchange method and apparatus of configurable combination |
Non-Patent Citations (1)
| Title |
|---|
| 汪峰坤;张婷婷;: "通用数据挖掘系统的结构与设计", 鸡西大学学报, no. 11 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113448742B (en) | 2023-11-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110381042B (en) | Graceful restart service method, device, medium and electronic equipment | |
| US11269705B2 (en) | Method and apparatus for outputting information | |
| CN111597065B (en) | Method and device for collecting equipment information | |
| CN111447170B (en) | Data processing method and system, computer system and computer readable medium | |
| CN111625422B (en) | Thread monitoring method, thread monitoring device, electronic equipment and computer readable storage medium | |
| CN110457132B (en) | Method and device for creating functional object and terminal equipment | |
| CN113076253A (en) | Test method and test device | |
| CN114398179B (en) | Method and device for acquiring tracking identifier, server and storage medium | |
| CN112948272A (en) | Production environment-based data test system function method and device and related equipment | |
| CN113641544B (en) | Method, apparatus, device, medium and product for detecting application state | |
| CN110881224B (en) | Network long connection method, device, equipment and storage medium | |
| CN109981546B (en) | Method and device for acquiring remote call relation between application modules | |
| CN110275701B (en) | Data processing method, device, medium and computing equipment | |
| CN111475230B (en) | Application function configuration method and device and electronic equipment | |
| CN116700779A (en) | Code dynamic adjustment method, device, equipment, medium and program product | |
| CN113448742B (en) | Interface data acquisition method and device | |
| CN111984496B (en) | Method, device, medium and electronic equipment for monitoring stack memory leakage | |
| CN113760693A (en) | Method and apparatus for local debugging of microservice systems | |
| CN115378792B (en) | Alarm processing method, device and storage medium | |
| CN111209058B (en) | Method, device, medium and equipment for acquiring process name | |
| CN110099122B (en) | Method and apparatus for sending network request | |
| CN109376023B (en) | Method and equipment for generating calling information and issuing return code group | |
| CN109388536B (en) | Data collection method and device | |
| CN116522200A (en) | Data circulation method, device, equipment, storage medium and product | |
| CN116501597A (en) | Code detection method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |