CN113760693A - Method and apparatus for local debugging of microservice systems - Google Patents
Method and apparatus for local debugging of microservice systems Download PDFInfo
- Publication number
- CN113760693A CN113760693A CN202010603618.2A CN202010603618A CN113760693A CN 113760693 A CN113760693 A CN 113760693A CN 202010603618 A CN202010603618 A CN 202010603618A CN 113760693 A CN113760693 A CN 113760693A
- Authority
- CN
- China
- Prior art keywords
- service
- monitored
- debugging
- configuration information
- generating
- 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/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
Abstract
The invention discloses a method and a device for local debugging of a microservice system, and relates to the technical field of computers. One embodiment of the method comprises: determining a strategy corresponding to a service to be monitored in the micro-service system; according to the strategy corresponding to the service to be monitored, collecting the configuration information of the service to be monitored; generating a calling request according to the configuration information; and monitoring the service to be monitored by utilizing the generalization mode and the calling request to generate a debugging result. The implementation mode overcomes the technical defect that a plurality of test environments of the service are lacked in dependence in the prior art, and further achieves the technical effect of flexibly calling the pre-release service or the test environment.
Description
Technical Field
The invention relates to the technical field of computers, in particular to local debugging for a micro-service system.
Background
When a problem occurs in function development or on line, the code needs to be debugged, and whether the code is correct or not needs to be verified after the code is modified. The prior art mainly adopts the following method for debugging:
the method 1 is characterized in that simulation service is carried out on the service to be monitored, and then debugging of the micro service system is realized;
mode 2, increasing a debugging log, deploying a pre-release environment, and further realizing debugging of the micro service system;
in the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
the method 1 needs simulation service for all scenes;
approach 2 requires the ability to rely on engineers, should the environment be redeployed for each commissioning.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for local debugging of a microservice system, which can achieve the technical effect of flexibly invoking a pre-release service or a test environment.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a method for local debugging of a microservice system, including:
determining a strategy corresponding to a service to be monitored in the micro-service system;
according to the strategy corresponding to the service to be monitored, collecting the configuration information of the service to be monitored;
generating a calling request according to the configuration information;
and monitoring the service to be monitored by utilizing the generalization mode and the calling request to generate a debugging result.
Optionally, before determining the policy corresponding to the service to be monitored in the microservice system, the method includes:
adding annotations to services to be monitored in the micro service system;
the attribute corresponding to the annotation comprises a strategy corresponding to the service to be monitored and a remark corresponding to the strategy.
Optionally, the configuration information includes: service name, service packet, timeout time, number of retries, service protocol.
Optionally, generating, according to the configuration information, a call request, including:
analyzing the configuration information to generate request information;
and generating a calling request according to the request information.
Optionally, generating a debugging result by using the generalization mode and the call request, including:
and calling the service to be monitored by utilizing the generalization mode, carrying out JSON serialization according to the calling request, and returning to the client agent.
Optionally, after the generating the debugging result, the method includes:
if the debugging result is successful, performing deserialization on the debugging result, and returning the deserialized result;
and if the debugging result is abnormal, generating abnormal information according to the abnormal information and the generated stack information.
According to still another aspect of an embodiment of the present invention, there is provided an apparatus for local debugging of a microservice system, including:
the strategy determining module is used for determining a strategy corresponding to a service to be monitored in the micro service system;
the configuration information collection module is used for collecting the configuration information of the service to be monitored according to the strategy corresponding to the service to be monitored;
the calling request generating module is used for generating a calling request according to the configuration information;
and the debugging result generation module is used for monitoring the service to be monitored by utilizing the generalization mode and the calling request to generate a debugging result.
Optionally, before determining the policy corresponding to the service to be monitored in the microservice system, the method includes:
adding annotations to services to be monitored in the micro service system;
the attribute corresponding to the annotation comprises a strategy corresponding to the service to be monitored and a remark corresponding to the strategy.
Optionally, the configuration information includes: service name, service packet, timeout time, number of retries, service protocol.
Optionally, generating, according to the configuration information, a call request, including:
analyzing the configuration information to generate request information;
and generating a calling request according to the request information.
Optionally, generating a debugging result by using the generalization mode and the call request, including:
and calling the service to be monitored by utilizing the generalization mode, carrying out JSON serialization according to the calling request, and returning to the client agent.
Optionally, after the generating the debugging result, the method includes:
if the debugging result is successful, performing deserialization on the debugging result, and returning the deserialized result;
and if the debugging result is abnormal, generating abnormal information according to the abnormal information and the generated stack information.
According to another aspect of the embodiments of the present invention, there is provided an electronic device for local debugging of a microservice system, including:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method for local debugging of a microservice system provided by the present invention.
According to a further aspect of embodiments of the present invention, there is provided a computer-readable medium, on which a computer program is stored, which, when executed by a processor, implements the method for local debugging of a microservice system provided by the present invention.
One embodiment of the above invention has the following advantages or benefits:
the technical defect that a plurality of test environments of the service are lacked in dependence in the prior art is overcome by the technical means of debugging locally, and the technical effect of flexibly calling the pre-release service or the test environment is achieved.
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 diagram of a main flow of a method for local debugging of a microservice system in accordance with an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating an embodiment of a method for local debugging of a microservice system, in accordance with the present invention;
FIG. 3 is a schematic diagram of the main blocks of an apparatus for local debugging of a microservice system in accordance with 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 in implementing a terminal device or server of 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.
Fig. 1 is a schematic diagram of a main flow of a method for local debugging of a microservice system according to an embodiment of the present invention, as shown in fig. 1, including:
s101, determining a strategy corresponding to a service to be monitored in a micro service system;
step S102, collecting configuration information of the service to be monitored according to a strategy corresponding to the service to be monitored;
step S103, generating a calling request according to the configuration information;
and S104, monitoring the service to be monitored by utilizing the generalization mode and the calling request to generate a debugging result.
In practical applications, the strategies to be monitored mainly include: invoking a pre-release environment service and invoking a test environment. Specifically, the policy may be to invoke the pre-release environment service to number 1 and the invocation test environment to number 2. For example, the annotations added in the annotation of the service to be monitored are: @ Monitor (strateg5 ═ 1, remark ═ proxy xxx service').
Wherein the configuration information comprises at least one of: service name, service packet, timeout time, number of retries, service protocol. The service monitored by the call request can be limited by the configuration information, for example, whether the service to be monitored exists or not is monitored according to the timeout time.
The technical defect that a plurality of test environments of the service are lacked in dependence in the prior art is overcome by the technical means of debugging locally, and the technical effect of flexibly calling the pre-release service or the test environment is achieved.
Optionally, before determining the policy corresponding to the service to be monitored in the microservice system, the method includes:
adding annotations to services to be monitored in the micro service system;
the attribute corresponding to the annotation comprises a policy (strategy) corresponding to the service to be monitored and a remark (remap) corresponding to the policy.
In practical application, the information of the service to be monitored can be collected through a client agent, and the calling of the service to be monitored can be realized through a strategy corresponding to the service.
Specifically, when the policy corresponding to the service to be monitored is to invoke the pre-release environment service, information corresponding to the service may be collected, for example, a service registration center, a service name, a service group, a service protocol, and the like, and subsequently, the collected information JSON may be serialized and send a request to the server. And after the customer service end acquires the response, analyzing the data and serving as the response of the dependent service.
When the policy corresponding to the service to be monitored is set for calling the test environment, the service may not be processed, that is, the content of the annotation is ignored. Specifically, the invocation of all steps may be proxied in the manner of a proxy.
Optionally, generating, according to the configuration information, a call request, including:
analyzing the configuration information to generate request information;
and generating a calling request according to the request information.
Optionally, generating a debugging result by using the generalization mode and the call request, including:
and calling the service to be monitored by utilizing the generalization mode, carrying out JSON serialization according to the calling request, and returning to the client agent.
The generalization mode is mainly used for the condition that a consumption end does not have an API (application program interface); the method does not need to introduce an interface jar package (Java archive file), but directly initiates a service call through a GenericService interface, and Java objects in parameters and return values are represented by Map.
Specifically, the generalized call does not need to pay attention to the service end, and the exposure can be performed according to normal services. The coupling degree between algorithms can be reduced by calling the service to be monitored by adopting a generalization mode, so that the technical defect of high requirement degree on the algorithms is avoided, and the workload of programmers is reduced to the maximum extent.
Optionally, after the generating the debugging result, the method includes:
if the debugging result is successful, performing deserialization on the debugging result, and returning the deserialized result;
and if the debugging result is abnormal, generating abnormal information according to the abnormal information and the generated stack information.
The flow of the present application is described in detail below with a specific example. Assume that the service provided externally by the application is service a, which relies on service 1, service 2, and service 3. Fig. 2 is a schematic diagram of an embodiment of a method for local debugging of a microservice system according to the present invention, as shown in fig. 2, including:
step S201, the service A receives the request and processes the relevant parameters;
step S202, calling a service 1, triggering client agent monitoring, and if the strategy corresponding to the service 1 is set to be 2, calling a test environment service, directly releasing without any processing; otherwise, relevant configuration information of the service 1, such as service name, service packet, timeout time, retry number, service protocol, etc., is collected, information JSON is serialized, and an HTTP request is sent to the server. Request structure:
step S203, the server receives the request, analyzes the request information, assembles the call request according to the request information, uses the generalization mode to call the service 1 of the pre-release environment, assembles the information after receiving the response, serializes the JSON and returns the information to the client agent. At this time, the response of the generalization call may be an exception error, and the assembled information is also supporting this scenario.
Specifically, a successful response may be:
the failure response may be:
step S204, the client proxy acquires a response, whether the response is successful or not is judged according to a result flag (result _ flag), and if the response is successful, the data is deserialized and returned as a proxy response; otherwise, the abnormal information and the stack information are analyzed, and the abnormality is thrown out.
Step S205, continuing to execute the program code;
step S206, calling service 2 and service 3, and synchronizing step S202 to step S204;
step S207, continuing to execute subsequent codes;
and step S208, finishing the processing of the service A and responding to the outside.
FIG. 3 is a schematic diagram of the main blocks of an apparatus for local debugging of a microservice system in accordance with an embodiment of the present invention;
according to still another aspect of an embodiment of the present invention, there is provided an apparatus for local debugging of a microservice system, including:
a policy determining module 301, configured to determine a policy corresponding to a service to be monitored in the micro service system;
a configuration information collection module 302, configured to collect configuration information of the service to be monitored according to a policy corresponding to the service to be monitored;
a calling request generating module 303, configured to generate a calling request according to the configuration information;
and a debugging result generating module 304, configured to monitor the service to be monitored by using the generalization mode and the call request, and generate a debugging result.
Optionally, before determining the policy corresponding to the service to be monitored in the microservice system, the method includes:
adding annotations to services to be monitored in the micro service system;
the attribute corresponding to the annotation comprises a strategy corresponding to the service to be monitored and a remark corresponding to the strategy.
Optionally, the configuration information includes: service name, service packet, timeout time, number of retries, service protocol.
Optionally, generating, according to the configuration information, a call request, including:
analyzing the configuration information to generate request information;
and generating a calling request according to the request information.
Optionally, generating a debugging result by using the generalization mode and the call request, including:
and calling the service to be monitored by utilizing the generalization mode, carrying out JSON serialization according to the calling request, and returning to the client agent.
Optionally, after the generating the debugging result, the method includes:
if the debugging result is successful, performing deserialization on the debugging result, and returning the deserialized result;
and if the debugging result is abnormal, generating abnormal information according to the abnormal information and the generated stack information.
Fig. 4 illustrates an exemplary system architecture 400 for a local debugging method for a microservice system or a local debugging apparatus for a microservice system to which embodiments of the present 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. 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. The terminal devices 401, 402, 403 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
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. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.
It should be noted that the local debugging method for the micro service system provided by the embodiment of the present invention is generally executed by the server 405, and accordingly, the local debugging apparatus for the micro service system 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 module (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 module (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 includes a sending module, an obtaining module, a determining module, and a first processing module. The names of these modules do not form a limitation on the modules themselves in some cases, and for example, the sending module may also be described as a "module sending a picture acquisition request to a connected server".
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:
determining a strategy corresponding to a service to be monitored in the micro-service system;
according to the strategy corresponding to the service to be monitored, collecting the configuration information of the service to be monitored;
generating a calling request according to the configuration information;
and monitoring the service to be monitored by utilizing the generalization mode and the calling request to generate a debugging result.
According to the technical scheme of the embodiment of the invention, the following technical effects can be achieved:
the technical defect that a plurality of test environments of the service are lacked in dependence in the prior art is overcome by the technical means of debugging locally, and the technical effect of flexibly calling the pre-release service or the test environment is achieved.
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 (9)
1. A method for local debugging of a microservice system, comprising:
determining a strategy corresponding to a service to be monitored in the micro-service system;
according to the strategy corresponding to the service to be monitored, collecting the configuration information of the service to be monitored;
generating a calling request according to the configuration information;
and monitoring the service to be monitored by utilizing the generalization mode and the calling request to generate a debugging result.
2. The method of claim 1, wherein before determining the policy corresponding to the service to be monitored in the microservice system, the method comprises:
adding annotations to services to be monitored in the micro service system;
the attribute corresponding to the annotation comprises a strategy corresponding to the service to be monitored and a remark corresponding to the strategy.
3. The method of claim 1, wherein the configuration information comprises: service name, service packet, timeout time, number of retries, service protocol.
4. The method of claim 1, wherein generating a call request based on the configuration information comprises:
analyzing the configuration information to generate request information;
and generating a calling request according to the request information.
5. The method of claim 1, wherein generating a debug result using a generalization pattern and the call request comprises:
and calling the service to be monitored by utilizing the generalization mode, carrying out JSON serialization according to the calling request, and returning to the client agent.
6. The method according to one of claims 1 to 5, wherein after generating the debug result, comprising:
if the debugging result is successful, performing deserialization on the debugging result, and returning the deserialized result;
and if the debugging result is abnormal, generating abnormal information according to the abnormal information and the generated stack information.
7. An apparatus for local debugging of a microservice system, comprising:
the strategy determining module is used for determining a strategy corresponding to a service to be monitored in the micro service system;
the configuration information collection module is used for collecting the configuration information of the service to be monitored according to the strategy corresponding to the service to be monitored;
the calling request generating module is used for generating a calling request according to the configuration information;
and the debugging result generation module is used for monitoring the service to be monitored by utilizing the generalization mode and the calling request to generate a debugging result.
8. An electronic device for local debugging of a microservice system, 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-6.
9. 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-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010603618.2A CN113760693A (en) | 2020-06-29 | 2020-06-29 | Method and apparatus for local debugging of microservice systems |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010603618.2A CN113760693A (en) | 2020-06-29 | 2020-06-29 | Method and apparatus for local debugging of microservice systems |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113760693A true CN113760693A (en) | 2021-12-07 |
Family
ID=78785459
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010603618.2A Pending CN113760693A (en) | 2020-06-29 | 2020-06-29 | Method and apparatus for local debugging of microservice systems |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113760693A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115633073A (en) * | 2022-09-02 | 2023-01-20 | 易保网络技术(上海)有限公司 | Micro-service calling method, electronic device, system and readable storage medium |
-
2020
- 2020-06-29 CN CN202010603618.2A patent/CN113760693A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115633073A (en) * | 2022-09-02 | 2023-01-20 | 易保网络技术(上海)有限公司 | Micro-service calling method, electronic device, system and readable storage medium |
| CN115633073B (en) * | 2022-09-02 | 2023-11-14 | 易保网络技术(上海)有限公司 | Micro-service calling method, electronic device, system and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9529691B2 (en) | Monitoring and correlating a binary process in a distributed business transaction | |
| CN107644075B (en) | Method and device for collecting page information | |
| CN111786939B (en) | Method, device and system for testing management platform of Internet of things | |
| CN113900834B (en) | Data processing method, device, equipment and storage medium based on Internet of things technology | |
| CN111045833A (en) | Interface calling method and device | |
| CN112084042B (en) | Message processing method and device | |
| CN110896362A (en) | Fault detection method and device | |
| CN112445860B (en) | Method and device for processing distributed transaction | |
| CN113760693A (en) | Method and apparatus for local debugging of microservice systems | |
| CN110275701B (en) | Data processing method, device, medium and computing equipment | |
| CN113760487B (en) | Service processing method and device | |
| CN112131095B (en) | Pressure testing method and device | |
| CN114979295A (en) | Gateway management method and device | |
| CN111460020B (en) | Method, device, electronic equipment and medium for resolving message | |
| CN113779122A (en) | Method and apparatus for exporting data | |
| CN113761433A (en) | Service processing method and device | |
| CN112532734A (en) | Message sensitive information detection method and device | |
| CN113326060A (en) | Service request processing method, device and system and service configuration method and device | |
| CN113779018A (en) | Data processing method and device | |
| CN112860447A (en) | Interaction method and system between different applications | |
| CN111698109A (en) | Method and device for monitoring log | |
| CN112948430B (en) | Date data query method and device | |
| CN113778969A (en) | Log processing method and device | |
| CN109388536B (en) | Data collection method and device | |
| CN115048279A (en) | Server processing method and device, electronic equipment and computer readable 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 |