WO2020186773A1 - Procédé, dispositif et appareil de surveillance de demandes d'appel, et support d'informations - Google Patents

Procédé, dispositif et appareil de surveillance de demandes d'appel, et support d'informations Download PDF

Info

Publication number
WO2020186773A1
WO2020186773A1 PCT/CN2019/116471 CN2019116471W WO2020186773A1 WO 2020186773 A1 WO2020186773 A1 WO 2020186773A1 CN 2019116471 W CN2019116471 W CN 2019116471W WO 2020186773 A1 WO2020186773 A1 WO 2020186773A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
call request
interface call
class object
identifier
Prior art date
Application number
PCT/CN2019/116471
Other languages
English (en)
Chinese (zh)
Inventor
杜亚明
王礼
宋邦勇
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020186773A1 publication Critical patent/WO2020186773A1/fr

Links

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/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
    • G06F11/3428—Benchmarking
    • 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/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4416—Network booting; Remote initial program loading [RIPL]

Definitions

  • This application relates to the field of network communication technology, and in particular to a method, device, device, and storage medium for calling request monitoring.
  • Twitter's zipkin currently only for spring
  • the cloud system is well integrated and lacks web service support for springboot and tomcat; the default is to use the hypertext transfer protocol (http) to request information to be reported to zipkin, which costs a lot of energy.
  • http hypertext transfer protocol
  • the main purpose of this application is to provide a method, device, device, and storage medium for call request monitoring, which aims to solve the problem that the prior art cannot simply and effectively implement the monitoring of call requests, which leads to the difficult development of the actual process of request monitoring and high cost of energy consumption.
  • this application provides a call request monitoring method, which includes the following steps:
  • a request identifier corresponding to the interface call request is generated according to a preset identifier generation rule, the interface call request is marked according to the request identifier, and the marked interface call request is forwarded.
  • the step of detecting whether the class object is a preset interception object includes:
  • the set of interception objects contains several interception object identifiers corresponding to objects of the class to be intercepted;
  • the step of performing bytecode enhancement on the class object and intercepting the interface call request through the class object after the bytecode enhancement includes:
  • Method aspect interception is performed on the interface call request according to the class object after bytecode enhancement.
  • the method further includes:
  • the method further includes:
  • the step of generating a request identifier corresponding to the interface call request according to a preset identifier generation rule includes:
  • a character with a preset number of bits is selected from the Internet Protocol address, the character and the media access control address are combined, and the combined result is used as the request identifier corresponding to the interface call request.
  • the step of generating a request identifier corresponding to the interface call request according to a preset identifier generation rule further includes:
  • this application also proposes a request invocation link monitoring device, which includes:
  • the object obtaining module is used to obtain the class object corresponding to the interface call request when the interface call request initiated by the application service is detected;
  • the request interception module is used to detect whether the class object is a preset interception object, and if so, perform bytecode enhancement on the class object, and intercept the interface call request through the bytecode-enhanced class object;
  • the request marking module is configured to generate a request identifier corresponding to the interface call request according to a preset identifier generation rule, mark the interface call request according to the request identifier, and forward the marked interface call request.
  • this application also proposes a call request monitoring device, the device including: a memory, a processor, and computer-readable instructions stored in the memory and running on the processor, so When the computer-readable instructions are executed by the processor, the processor is caused to execute the steps of invoking the request monitoring method as described above.
  • this application also proposes a storage medium that stores computer-readable instructions on the storage medium.
  • the processor executes the The steps of calling the request monitoring method.
  • This application obtains the class object corresponding to the interface call request when the interface call request initiated by the application service is detected; detects whether the class object is a preset interception object, and if so, performs bytecode enhancement on the class object, and passes the word
  • the code-enhanced class object intercepts the interface call request; then generates the request identifier corresponding to the interface call request according to the preset identifier generation rule, then marks the interface call request according to the request identifier, and performs the marked interface call request Forwarding, because it intercepts and detects the class object corresponding to the request, the class object is enhanced when it needs to be intercepted, and then the request is intercepted through the enhanced class object and the corresponding request identifier is marked, so that the call can be realized
  • the comprehensive monitoring of requests reduces the development difficulty and cost of energy consumption during the realization of request monitoring.
  • FIG. 1 is a schematic structural diagram of a call request monitoring device of a hardware operating environment involved in a solution of an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a first embodiment of a method for monitoring a call request of this application
  • FIG. 3 is a schematic flowchart of a second embodiment of a method for monitoring a call request of this application
  • FIG. 4 is a schematic flowchart of a third embodiment of a method for monitoring a call request of this application.
  • Fig. 5 is a structural block diagram of the first embodiment of the calling request monitoring device of this application.
  • FIG. 1 is a schematic structural diagram of a call request monitoring device of a hardware operating environment involved in a solution of an embodiment of the application.
  • the call request monitoring device may include: a processor 1001, such as a central processing unit (Central Processing Unit). Unit, CPU), communication bus 1002, user interface 1003, network interface 1004, memory 1005.
  • the communication bus 1002 is used to implement connection and communication between these components.
  • the user interface 1003 may include a display screen (Display) and an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface.
  • the network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (WIreless-FIdelity, WI-FI) interface).
  • WIreless-FIdelity WI-FI
  • the memory 1005 may be a high-speed random access memory (Random Access Memory, RAM) memory, can also be a stable non-volatile memory (Non-Volatile Memory, NVM), such as disk storage.
  • RAM Random Access Memory
  • NVM Non-Volatile Memory
  • the memory 1005 may also be a storage device independent of the foregoing processor 1001.
  • FIG. 1 does not constitute a limitation on the call request monitoring device, and may include more or fewer components than shown in the figure, or a combination of certain components, or different component arrangements.
  • the memory 1005 as a storage medium may include an operating system, a data storage module, a network communication module, a user interface module, and computer readable instructions.
  • the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with users; this application calls the processor 1001 in the request monitoring device 1005 may be set in a call request monitoring device that calls computer-readable instructions stored in the memory 1005 through the processor 1001 and executes the call request monitoring method provided in the embodiment of the present application.
  • the embodiment of the present application provides a method for monitoring a call request.
  • FIG. 2 is a schematic flowchart of a first embodiment of the method for monitoring a call request of this application.
  • the call request monitoring method includes the following steps:
  • Step S10 when an interface call request initiated by an application service is detected, obtain a class object corresponding to the interface call request;
  • the class object may be a method of a class.
  • Class is an object-oriented programming (OOP, Object-Oriented) Programming) The basis for information encapsulation.
  • OOP object-oriented programming
  • Each class contains data description and a set of functions (or methods) for operating data or transferring messages.
  • the instances of the class are called objects.
  • the application service can be either the recipient of the call request or the initiator of the call request.
  • application service a needs to call the interface of application service b, and application service b is making a call request to application service a.
  • the application service c needs to be called, and then the application service b is both the receiver and the initiator of the call request.
  • the application service needs to be connected to the APM platform in advance.
  • the application service may be a client or a server, and its category may be determined according to specific application scenarios.
  • the APM platform when the APM platform detects that an accessed application service initiates an interface call request to another application service, it can first parse the interface call request, and then obtain the class object corresponding to the request according to the analysis result.
  • Step S20 Detect whether the class object is a preset interception object, and if so, perform bytecode enhancement on the class object, and intercept the interface call request through the bytecode-enhanced class object;
  • Java probes can achieve specific code capture, function (or method) execution time-consuming range capture, function ( Or method) call monitoring and other operations.
  • the preset interception object may be preset methods of various types that need to be intercepted by executing method aspects.
  • the R&D personnel can extract in advance the object identifier corresponding to the interception object that needs to be intercepted by the method aspect and store it in a specific interception object set, so that the APM platform can detect whether the class object needs to be intercepted.
  • intercepting perform rapid detection based on the intercepted object set.
  • the APM platform may obtain the target object identifier corresponding to the class object; then read the pre-configured interception object set, and the interception object set contains several interception object identifiers corresponding to the class objects to be intercepted; And it is detected whether the target object identifier belongs to the interception object identifier.
  • the APM platform in this embodiment can call the pre-configured bytecode enhancement plug-in "byte-buddy" Binary modification is performed on the class object, and then interceptors are added to the modified class object and method aspects are defined to obtain the enhanced class object.
  • the APM platform can call the preset bytecode enhancement plug-in Binary modification is performed on the Java class in the class object, and an interceptor is added to the modified class object to obtain the bytecode-enhanced class object. Then, the method aspect interception is performed on the interface call request according to the class object after the bytecode enhancement.
  • Step S30 Generate a request identifier corresponding to the interface call request according to a preset identifier generation rule, mark the interface call request according to the request identifier, and forward the marked interface call request.
  • the request identifier may be an identification code or identification character that can distinguish different call requests.
  • the preset generation rule is a pre-defined request identifier generation strategy, for example, it may be based on the Internet Protocol address (IP address) carried in the request or the media access control address (MAC address) corresponding to the hardware device where the request initiator is located.
  • IP address Internet Protocol address
  • MAC address media access control address
  • the request identifier is generated, which is not limited in this embodiment.
  • the APM platform in this embodiment can obtain the media access control address corresponding to the application service and the Internet protocol address corresponding to the interface call request; from the Internet Protocol address A character with a preset number of digits is selected, the character and the media access control address are combined, and the combined result is used as the request identifier corresponding to the interface call request.
  • the selection of characters with a preset number of digits from the Internet Protocol address may be the selection of the last four characters in the IP address.
  • APM first extracts the MAC address The number "444553540000” in and the last four digits "2140" in the IP address, and then combine the two to obtain the combined request identifier "4445535400002140".
  • the method for generating the request identifier can also be that the APM platform obtains the media access control address corresponding to the application service and the request initiation time corresponding to the interface invocation request; Time format conversion to obtain the corresponding timestamp; combine the media access control address and the timestamp to obtain a combined character, input the combined character into a preset hash function, and output the result of the obtained function As the request identifier corresponding to the interface call request.
  • the application service usually adopts a 24-hour system or a 12-hour system.
  • the APM platform in this embodiment will convert the time format of the obtained request initiation time and convert it to the corresponding
  • the timestamp in this embodiment is preferably a unix timestamp.
  • the request was initiated time 2018-09-19 15:33:19, converted to Unix timestamp is 1537342399.
  • the hash function is a Hash function, which can transform an input of any length into a fixed-length output through a hash algorithm, and the output is a hash value.
  • the Hash algorithm is applied to the generation of the request identifier to ensure the uniqueness of the generated request identifier.
  • APM generates a unique request identifier for the interface call request according to the preset identifier generation rule, then marks the interface call request according to the request identifier, and then sends the interface call request according to the access address carried in the request To the next hop application service.
  • This embodiment obtains the class object corresponding to the interface call request when the interface call request initiated by the application service is detected; detects whether the class object is a preset interception object, and if so, performs bytecode enhancement on the class object, and passes The class object after bytecode enhancement intercepts the interface call request; then generates the request identifier corresponding to the interface call request according to the preset identifier generation rule, and then marks the interface call request according to the request identifier, and the marked interface call request For forwarding, because it intercepts and detects the class object corresponding to the request, the class object is enhanced when it needs to be intercepted, and then the request is intercepted through the enhanced class object and the corresponding request identifier is marked, so that the The comprehensive monitoring of call requests reduces the development difficulty and cost of energy consumption in the process of request monitoring realization.
  • FIG. 3 is a schematic flowchart of a second embodiment of a call request monitoring method according to this application.
  • the method further includes:
  • Step S40 Search the log file corresponding to the interface call request in the storage space of the application service, and mark the log file according to the request identifier;
  • the APM platform in order to facilitate the subsequent APM platform to view the request link of each call request, when the APM platform intercepts the call request, it will be on the application service side that initiated the call request and the application responding to the call request.
  • the server side generates a monitoring log (that is, the log file), and the monitoring log carries the request identifier corresponding to the call request; of course, the APM platform detects that the application server side responding to the call request is performing the request
  • an additional monitoring log about database access will be generated in the application service.
  • the request identifier corresponding to the interface call request is generated by the APM product platform, the log file of the application service that originally initiated the interface call request does not carry the request identifier. Therefore, the APM platform in this embodiment is detecting When the response to the interface call request is completed, the log file corresponding to the interface call request is searched in the storage space of the application service that initiated the interface call request, and the log file is marked according to the request identifier.
  • Step S50 Call the preset log collection component to collect all log files carrying the request identifier in real time, and upload the collected log files to the distributed message system for storage.
  • the preset log collection component may be a pre-configured component for collecting request log files.
  • the preset log collection component is preferably a Flume component
  • Flume is a Cloudera (one An open source platform) provides a highly available, highly reliable, distributed system for massive log collection, aggregation, and transmission. Flume supports customizing various data senders in the log system to collect data; at the same time, Flume provides The ability to simply process data and write to various data recipients (customizable).
  • the distributed message system may be a log analysis platform or system.
  • the ELK platform (ELK, Elasticsearch Logstash Kibana), Elasticsearch is an open source distributed search engine that provides three functions of collecting, analyzing, and storing data; Logstash is mainly a tool for collecting, analyzing, and filtering logs, supporting a large number of data acquisition methods; Kibana Can be Logstash
  • the log analysis and friendly web interface provided by ElasticSearch can help summarize, analyze and search important data logs.
  • the APM platform can call the Flume component to search for the corresponding log file in the application services involved in the entire request life cycle of the interface call request based on the request identifier, and upload the found log file to The Kafka platform is then sent by the Kafka platform to the distributed message system for storage.
  • the Kafka platform is a distributed streaming media platform, which is mostly used to build reliable pipelines for transmitting real-time data between systems or applications, and to build real-time streaming data processing programs to transform or process data streams.
  • the Kafka platform After the Kafka platform receives the log files, it first generates corresponding message queues based on these log files, and then Logstash in the ELK platform consumes the message queues, and then consumes them through the Filter plug-in The latter data is redefined by the time object, and then a request invocation link corresponding to the interface invocation request is generated according to the redefined data, and the request invocation link is saved.
  • the log file corresponding to the interface call request is found in the storage space of the application service, and the log file is marked according to the request identifier; the preset log collection component is called to collect all log files carrying the request identifier in real time, and collect
  • the received log files are uploaded to the distributed message system for storage, which has more efficient storage and faster retrieval methods than traditional database storage methods.
  • FIG. 4 is a schematic flowchart of a third embodiment of a call request monitoring method according to this application.
  • the method further includes:
  • Step S60 when receiving the call link check instruction, extract the target request identifier contained in the call link check instruction;
  • the R&D personnel when they need to view the entire call link of a call request, they can send the call link view instruction to the APM platform, and when the APM platform receives In this instruction, the instruction is first parsed, and then the request identifier corresponding to the call request that needs to be viewed carried in the instruction, that is, the target request identifier, is extracted.
  • Step S70 Read the corresponding request log file from the distributed messaging system according to the target request identifier, and read the time and date parameters contained in the log file;
  • the request log corresponding to each call request in this embodiment is stored in the distributed messaging system, when the APM platform needs to view the request log, the APM platform can use the target request identifier from the Read the corresponding request log file in the distributed message system.
  • time and date parameter may be the generation time of the request log file carried in the request log file, which may be used to represent the approximate time for the application service to respond to the received request.
  • the APM platform can read the corresponding request log file from the distributed messaging system according to the target request identifier, and read the time and date contained in the log file parameter.
  • Step S80 Sort the request log files according to the time and date parameters, and display the sorted request log files.
  • APM will sort all the request log files obtained according to the time and date parameters in the request log file, and then display the request log files in chronological order for viewing.
  • This embodiment extracts the target request identifier contained in the call link view instruction when the call link view instruction is received; reads the corresponding request log file from the distributed messaging system according to the target request identifier, and reads the log file The time and date parameters included in the file; sort the request log files according to the time and date parameters, and display the sorted request log files, which can visually display the request log files for subsequent troubleshooting.
  • the embodiment of the present application also proposes a storage medium, and the storage medium may be a non-volatile readable storage medium.
  • the storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of calling the request monitoring method as described above are realized.
  • the method implemented when the computer-readable instruction is executed can refer to the various embodiments of the calling request monitoring method of this application, which will not be repeated here.
  • FIG. 5 is a structural block diagram of a first embodiment of a calling request monitoring device according to this application.
  • the call request monitoring device proposed in the embodiment of the present application includes:
  • the object obtaining module 501 is configured to obtain the class object corresponding to the interface call request when the interface call request initiated by the application service is detected;
  • the request interception module 502 is used to detect whether the class object is a preset interception object, and if so, perform bytecode enhancement on the class object, and intercept the interface call request through the bytecode-enhanced class object ;
  • the request marking module 503 is configured to generate a request identifier corresponding to the interface call request according to a preset identifier generation rule, mark the interface call request according to the request identifier, and forward the marked interface call request.
  • This embodiment obtains the class object corresponding to the interface call request when the interface call request initiated by the application service is detected; detects whether the class object is a preset interception object, and if so, performs bytecode enhancement on the class object, and passes The class object after bytecode enhancement intercepts the interface call request; then generates the request identifier corresponding to the interface call request according to the preset identifier generation rule, and then marks the interface call request according to the request identifier, and the marked interface call request For forwarding, because it intercepts and detects the class object corresponding to the request, the class object is enhanced when it needs to be intercepted, and then the request is intercepted through the enhanced class object and the corresponding request identifier is marked, so that the The comprehensive monitoring of call requests reduces the development difficulty and cost of energy consumption in the process of request monitoring realization.
  • the request interception module 502 is also used to obtain the target object identifier corresponding to the class object; read a pre-configured set of interception objects, and the set of interception objects contains several objects corresponding to the class to be intercepted. Interception object identification; detecting whether the target object identification belongs to the interception object identification.
  • the request interception module 502 is also used to call a preset bytecode enhancement plug-in to binary-modify the Java class in the class object, and add an interceptor to the modified class object to obtain bytes Code-enhanced class object; according to the bytecode-enhanced class object, method aspect interception is performed on the interface call request.
  • the call request monitoring device in this embodiment further includes a log collection module configured to search for the log file corresponding to the interface call request in the storage space of the application service, and according to all The request identifier marks the log file; the preset log collection component is called to collect all log files carrying the request identifier in real time, and the collected log files are uploaded to the distributed message system for storage.
  • a log collection module configured to search for the log file corresponding to the interface call request in the storage space of the application service, and according to all The request identifier marks the log file; the preset log collection component is called to collect all log files carrying the request identifier in real time, and the collected log files are uploaded to the distributed message system for storage.
  • the log collection module is further configured to extract the target request identifier contained in the call link view instruction when the call link view instruction is received; according to the target request identifier, from the distributed message system
  • the corresponding request log file is read in the log file, and the time and date parameters contained in the log file are read; the request log files are sorted according to the time and date parameters, and the sorted request log files are displayed.
  • the request marking module 503 is also used to obtain the media access control address corresponding to the application service and the internet protocol address corresponding to the interface call request; select a preset number of characters from the internet protocol address To combine the characters and the media access control address, and use the combined result as the request identifier corresponding to the interface call request.
  • the request marking module 503 is also used to obtain the media access control address corresponding to the application service and the request initiation time corresponding to the interface call request; convert the time format of the request initiation time to obtain the corresponding Timestamp; combine the media access control address and the timestamp to obtain a combined character, input the combined character into a preset hash function, and use the obtained function output result as the interface call request correspondence The request ID.
  • the method of the embodiment can be implemented by means of software plus a necessary general hardware platform, of course, it can also be implemented by hardware, but the former is a better implementation in many cases.
  • the application s The essence of the technical solution or the part that contributes to the existing technology can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium (such as read-only memory/random access memory, magnetic disk, optical disk).
  • the disk includes several instructions to enable a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the method described in each embodiment of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Quality & Reliability (AREA)
  • Mathematical Physics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Debugging And Monitoring (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé, un dispositif et un appareil de surveillance de demandes d'appel, et un support d'informations. Le procédé comprend les étapes suivantes : lors de la détection d'une demande d'appel d'interface lancée par un service d'application, acquérir un objet de classe correspondant à la demande d'appel d'interface (S10) ; détecter si l'objet de classe est un objet d'interception prédéfini, et si tel est le cas, réaliser une amélioration de code à octets sur l'objet de classe et intercepter la demande d'appel d'interface au moyen de l'objet de classe pourvu de l'amélioration du code à octets (S20) ; et générer, selon une règle de génération d'identifiant prédéfinie, un identifiant de demande correspondant à la demande d'appel d'interface, étiqueter la demande d'appel d'interface selon l'identifiant de demande et transférer la demande d'appel d'interface étiquetée (S30). L'invention met en oeuvre une détection d'interception sur un objet de classe correspondant à une demande, réalise une amélioration de classe sur l'objet de classe si l'interception de la demande est requise, et intercepte la demande au moyen de l'objet de classe amélioré et l'étiquette à l'aide d'un identifiant de demande correspondant, ce qui permet d'assurer une surveillance complète de demandes d'appel et de réduire les difficultés de développement et le surdébit de performance pendant un processus de mise en oeuvre de surveillance de demandes.
PCT/CN2019/116471 2019-03-16 2019-11-08 Procédé, dispositif et appareil de surveillance de demandes d'appel, et support d'informations WO2020186773A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910206045.7 2019-03-16
CN201910206045.7A CN110083391A (zh) 2019-03-16 2019-03-16 调用请求监控方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020186773A1 true WO2020186773A1 (fr) 2020-09-24

Family

ID=67413274

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/116471 WO2020186773A1 (fr) 2019-03-16 2019-11-08 Procédé, dispositif et appareil de surveillance de demandes d'appel, et support d'informations

Country Status (2)

Country Link
CN (1) CN110083391A (fr)
WO (1) WO2020186773A1 (fr)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110083391A (zh) * 2019-03-16 2019-08-02 平安科技（深圳）有限公司 调用请求监控方法、装置、设备及存储介质
CN112261072B (zh) * 2019-10-10 2024-04-09 北京京东尚科信息技术有限公司 一种服务调用方法、装置、设备和存储介质
CN110865927B (zh) * 2019-11-20 2021-08-31 腾讯科技（深圳）有限公司 区块链调用链路异常检测方法、装置和计算机设备
CN111488257A (zh) * 2020-04-14 2020-08-04 杭州云创共享网络科技有限公司 一种云服务链路跟踪监控方法、装置、设备及存储介质
CN112839096B (zh) * 2021-01-14 2022-07-22 深圳赛安特技术服务有限公司 监控函数执行时长的方法、装置、计算机设备及存储介质
CN113079048A (zh) * 2021-03-30 2021-07-06 深圳红途创程科技有限公司 数据采集方法、装置、计算机设备及存储介质
CN113051272A (zh) * 2021-03-30 2021-06-29 深圳红途创程科技有限公司 数据库表结构构建方法、装置、计算机设备及存储介质
CN113032221A (zh) * 2021-03-30 2021-06-25 深圳红途创程科技有限公司 数据采集和传输方法、装置、计算机设备及存储介质
CN113918770B (zh) * 2021-12-16 2022-03-25 上海冰鉴信息科技有限公司 字符串与时间字段的转换方法及装置
CN114253630B (zh) * 2021-12-23 2023-07-25 上海新炬网络信息技术股份有限公司 基于Java切面修改Form表单变化信息实现日志保存的方法
CN114285669A (zh) * 2021-12-31 2022-04-05 深圳昂楷科技有限公司 一种内嵌应用系统插件的水印嵌入方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101276271A (zh) * 2007-03-29 2008-10-01 北京邮电大学 一种面向切面编程的拦截器系统及方法
US20150378756A1 (en) * 2014-06-25 2015-12-31 SmartBear Software, Inc. Systems and methods for mobile application tracing instrumentation
CN107133171A (zh) * 2017-05-02 2017-09-05 山东浪潮通软信息科技有限公司 一种基于组件式的轻量aop框架及其使用方法
CN107291567A (zh) * 2017-06-20 2017-10-24 山东浪潮通软信息科技有限公司 一种数据调用方法、装置以及系统
CN110083391A (zh) * 2019-03-16 2019-08-02 平安科技（深圳）有限公司 调用请求监控方法、装置、设备及存储介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108763054B (zh) * 2018-04-17 2021-03-23 平安科技（深圳）有限公司 测试案例的测试效果展示方法、电子装置及存储介质
CN109474698A (zh) * 2018-12-14 2019-03-15 平安城市建设科技(深圳)有限公司 访问请求标记方法、装置、设备及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101276271A (zh) * 2007-03-29 2008-10-01 北京邮电大学 一种面向切面编程的拦截器系统及方法
US20150378756A1 (en) * 2014-06-25 2015-12-31 SmartBear Software, Inc. Systems and methods for mobile application tracing instrumentation
CN107133171A (zh) * 2017-05-02 2017-09-05 山东浪潮通软信息科技有限公司 一种基于组件式的轻量aop框架及其使用方法
CN107291567A (zh) * 2017-06-20 2017-10-24 山东浪潮通软信息科技有限公司 一种数据调用方法、装置以及系统
CN110083391A (zh) * 2019-03-16 2019-08-02 平安科技（深圳）有限公司 调用请求监控方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN110083391A (zh) 2019-08-02

Similar Documents

Publication Publication Date Title
WO2020186773A1 (fr) Procédé, dispositif et appareil de surveillance de demandes d'appel, et support d'informations
WO2020233077A1 (fr) Procédé, dispositif et appareil de surveillance de service de système et support d'informations
CN112738791B (zh) 基于5g核心网的用户信息关联回填方法、装置、设备和介质
WO2020224246A1 (fr) Procédé et appareil de gestion de données fondée sur une chaîne de blocs, dispositif et support d'informations
WO2013117104A1 (fr) Système et procédé de téléchargement de données hors ligne bt, et support de stockage informatique
WO2020253034A1 (fr) Procédé, appareil et dispositif de test de point enfoui client, et support d'enregistrement
WO2012060669A1 (fr) Procédé de commande d'un dispositif distant par l'intermédiaire de sms et dispositif associé
WO2018014580A1 (fr) Procédé et appareil de test d'interface de données, serveur et support de stockage
WO2021012489A1 (fr) Procédé d'interrogation de journal de plateforme téléphonique, dispositif terminal, support de stockage et appareil
WO2021169268A1 (fr) Procédé, appareil et dispositif de traitement de données, et support de stockage
WO2018107811A1 (fr) Procédé et appareil de défense conjointe pour la sécurité d'un réseau, serveur et support de stockage
WO2020015064A1 (fr) Procédé de traitement de défaillance de système, appareil, dispositif et support d'informations
WO2020233057A1 (fr) Procédé, appareil et dispositif d'empaquetage de fichiers, et support d'informations
WO2014054854A1 (fr) Système d'analyse de journal et procédé d'analyse de journal pour système de sécurité
WO2013174172A1 (fr) Procédé et système de prévisualisation d'informations de fichier
WO2019109957A1 (fr) Procédé, appareil, et dispositif de fourniture de service basé sur un bus de service d'entreprise (esb), et support d'informations lisible
WO2020077832A1 (fr) Procédé, appareil et dispositif d'accès à un bureau dans le nuage et support de stockage
WO2021072881A1 (fr) Procédé, appareil et dispositif de traitement de demande fondée sur un stockage d'objet, et support de stockage
WO2020233073A1 (fr) Procédé, dispositif et appareil de traitement de test d'environnement de chaîne de blocs, et support de stockage
WO2014112754A1 (fr) Procédé de pousser de service web, serveur de pousser de service web et serveur de fourniture de service web l'exécutant
WO2013094837A1 (fr) Procédé de gestion d'une distribution de charge de serveur par utilisation de résultats de fonction de hachage, et appareil correspondant
WO2020062658A1 (fr) Procédé et appareil de génération de contrat, dispositif et support de stockage
WO2015199271A1 (fr) Procédé et système de partage de fichiers sur p2p
WO2018036168A1 (fr) Procédé et dispositif d'exécution de tâche de traitement de données, serveur d'exécution et support de stockage
WO2017173838A1 (fr) Procédé d'affichage de message basé sur la vérification, et terminal de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19919765

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19919765

Country of ref document: EP

Kind code of ref document: A1